Add ST4 completions fields to reference #123
Merged
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
Remove redundant info. Add short description and example re `annotations` Added completions metadata section
michaelblyons
approved these changes
Feb 16, 2025
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.
I squashed and rebased #121 locally to make it easier to follow and added a few changes on top of it. Unfortunately, I cannot force-push to another person's PR branch, so a new PR will have to do.
Since we didn't have something in place to denote that something has been added with a certain build yet, I added something and also documented it in CONTRIBUTING.md. I also spent way to much time trying to figure out how the custom blocks feature works in vitepress exactly because I was getting conflicting information regarding which blocks are supported by default and why some didn't actually work (like
note). Ideally we'd add our own block instead of using markdown-it-attrs, but I didn't see an easy way for doing that.Supersedes and closes #121.