Add a JSON Schema for .ameba.yml and a CLI tool for automatically generating it
#497
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
|
That looks great, thanks! ❤️ I'll review it sometime in the upcoming days. |
|
How feasible would it be to make running this script / updating the schema a part of CI? That way ppl don't have to remember to run it for it to stay up to date. |
|
@nobodywasishere That certainly makes sense. It needs to be automated in order to make it hassle-free for the end-users. |
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.
When added to JSON Schema Store, this will allow autocomplete and documentation information for the
.ameba.ymlformat. Instead of writing one by-hand like was the case forshard.yml, instead I wrote a CLI tool that will automatically generate it and update it as new rules are added and changed.Screen.Recording.2024-11-17.at.09.36.12.mov