Add Extra Metadata about csproj file to Doc Source Generator & use for Package Links in Sample App #131
Conversation
Fix issue with Author missing Fix issue with old path setup for markdown file path
Can be used for Labs to mark experimental components when we interleave things together.
This will allow us to pass them into the generator and get additional info we can use in the Sample App for pointing folks towards Source code and Packages (for now).
Source code button navigates to component folder on GitHub (main branch) Most likely namespace is shown (hard-coded logic for now) - unoplatform/uno#8750 Shows and links to Uwp/WinUI packages on NuGet
michael-hawker
added
documentation 📃
Add future `experimental` frontmatter to docs from CommunityToolkit/Tooling-Windows-Submodule#131 Add TransitionHelper description to doc content (as was blank)
There was a problem hiding this comment.
Tested in UWP/Wasm, seems to work as expected save for this styling issue on WASM:
Also note that our current source generator was doing too much in a single place before this PR, iterating every type in every assembly on every keypress.
We should avoid adding to the source generator if there's an alternative (e.g. going through msbuild) so we don't worsen the tech debt here.
Approved to bring 8.0 closer to release.
|
@Arlodotexe there's a better approach @Sergio0694's taking in the MVVM Toolkit with a helper/API that just filters/grabs the attributed things directly. It's something we should switch to. But for the doc registry itself, we could probably move that to a separate step as it doesn't really need to be real time. |
Fixes #105
Tested in Windows repo with all the other changes here: CommunityToolkit/Windows#204
This PR:
experimentalbool to YAML FrontMatter of docs we can use for Labs-Windows in the future for interleaving repos for sample appscsprojfiles in AdditionalFiles to getComponentNameproperty as well as filename for packages identity