support extracting nu code snippets into standalone .nu files for better downstream trackability#2162
Open
orthonormalremy wants to merge 1 commit into
Open
Conversation
…ter downstream trackability
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.
There are many useful recipes that exist in the cookbook and there is no way to track them directly in a script-friendly way (markdown file parsing is not ideal obviously).
This PR adds support for useful standalone code snippets (e.g. snippets that someone might want to put in their
autoload/dir) to be extracted out into their own .nu files so it can remain the source of truth for the cookbook while also being programmatically fetch-able.Note: this PR uses the lightweight @vuepress/plugin-markdown-include plugin which is an official VuePress plugin from the same @vuepress/* family already used in this repo