Removes language saying that the developer extending Javy should fork the CLI and javy-core and clarify that they can fork them if they would like. Also add a code example of what extending Javy with additional JS APIs could look like.
Why am I making this change?
We got a question on Zulip that indicated the developer was not sure how to extend Javy and thought they needed to use a fork of our CLI so this provides an example and softens the language around forking.
Checklist
[x] I've updated the relevant CHANGELOG files if necessary. Changes to javy-cli and javy-core do not require updating CHANGELOG files.
Description of the change
Removes language saying that the developer extending Javy should fork the CLI and
javy-coreand clarify that they can fork them if they would like. Also add a code example of what extending Javy with additional JS APIs could look like.Why am I making this change?
We got a question on Zulip that indicated the developer was not sure how to extend Javy and thought they needed to use a fork of our CLI so this provides an example and softens the language around forking.
Checklist
javy-cliandjavy-coredo not require updating CHANGELOG files.