Documentation: make multi-code examples copy-paste ready#6688
Merged
Conversation
# Conflicts: # Documentation/Blazorise.Docs/Resources/docs-index.json
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 improves multi-code documentation examples by preserving their individual tabs while providing a single copy button that produces one complete, copy-paste-ready Razor component. Required models, services, validators, and supporting types are included in the component’s
@codeblock, while documentation-specific namespaces and dependencies are omitted.The behavior now covers DataGrid and other multi-code examples, including Autocomplete, DropdownList, ListView, FluentValidation, ModalProvider, and OffcanvasProvider examples. Existing example behavior, such as LocalStorage usage, is preserved.
The documentation compiler was also refactored so
CodeSnippetsonly coordinates snippet generation. Example-specific transformations are isolated in focused source composers behind a shared composition pipeline.