Add Local API Docs to be Pulled by Docs remote-content.mts
#1471
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
meaghanfitzgerald
added
the
DO NOT MERGE
meaghanfitzgerald
changed the title
remote-content.mts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why this should be merged
Stores local API documentation with subnet-evm
service.go. Subnet-EVM maintainers can update this file whenever there is a change to the API and changes will be reflected in the docs upon the following build.TO DO
validatorsAPI, and update existing documentationsubnet-evm/plugin/evm/service.mdto remote-content script in docs@federiconardelli7
How this works
Adds
service.mdcompatible with docs framework.How this was tested
NA
Need to be documented?
Yes?
Need to update RELEASES.md?
No