Render new conda-smithy linter documentation#2816
Draft
jaimergp wants to merge 6 commits intoconda-forge:mainfrom
Draft
Render new conda-smithy linter documentation#2816jaimergp wants to merge 6 commits intoconda-forge:mainfrom
jaimergp wants to merge 6 commits intoconda-forge:mainfrom
Conversation
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
2 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PR Checklist:
docs/orcommunity/, you have added it to the sidebar in the corresponding_sidebar.jsonfileNeeds conda-forge/conda-smithy#2408
We pre-fetch the linter JSON at build time to pre-render the TOC and populate the static search data; we then also fetch it again at runtime (each visit) in case there are updates since last visit (e.g. smithy got a new release but we haven't rebuilt the website yet). A new component parses the JSON and analyzes deprecation status to react to the toggle. Each category gets its own
Categorycomponent, which in turn renders theirMessagecomponents. There's a possibility for more dynamic filtering / searching but this is good enough for a start