fix: extension embedding example #792
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
|
/deploy-preview |
cderv
reviewed
Jul 21, 2023
Co-authored-by: Christophe Dervieux <[email protected]>
|
/deploy-preview |
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.
This PRs fixes and improves the documentation for extension embedding.
The example was to embed extension in an installed extension, which actually should never happen in user, but instead you want to embed extension when developping one.
In addition, the
jss/fancy-textexample now got adirectory tree to clearly show that embedding means adding an extension within an extension.This is related to quarto-dev/quarto-cli#6291