Improved README with better explanation of Hyperion & its features #225
Conversation
|
Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
|
||
| # Key Features | ||
|
|
||
| Brower API Virtualization: By using brower API's, Hyperion can create a virtualized development environment |
| the API response behavior. Through these different scenarios, developers have the ability to | ||
| test their code for unique edge cases or for specific inputs. | ||
|
|
||
| Performance Checking: The automatic monitoring of JavaScript classes and objects, can help |
There was a problem hiding this comment.
Is it worth mentioning here the performance impact of the virtualization itself? Or is that too down in the weeds?
|
Thanks for the contribution @nikhil-anantha13 . Could you please make sure to sign the CLA so I can proceed? |
facebook-github-bot
added
the
CLA Signed
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Edited the opening paragraph to better describe Hyperion and its purpose. Added the subsections of 'Key Features', 'How it works', and 'Use Cases', to provide detailed information on the features and functionality of Hyperion.