Repository navigation
feat: Avalonia components in the browser for the docs previews - #22
Merged
Merged
Conversation
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
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.
What
examples/Avalonia.Preview: the Avalonia components compiled to WebAssembly, showing one preview per address (?c=button,&theme=dark|light). It compiles the demo's own component files, so it can't drift from them.-p:PreviewsDir=<folder>; the four inPreviews/are samples.shelldocs-thememessages), and the app reports its content height.Merge with a merge commit: the docs site's Dockerfile pins
b3d98d4from this branch until it moves to main.Checked
dotnet build -c Release: 0 warnings, with and withoutPreviewsDir.