Repository navigation
docs: link the Nanoviews implementations from the examples and the DevTools page - #307
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #307 +/- ##
=======================================
Coverage 83.62% 83.62%
=======================================
Files 228 228
Lines 4849 4849
Branches 1074 1074
=======================================
Hits 4055 4055
Misses 553 553
Partials 241 241 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Why
Nanoviews 1.0.0 is out, and its repository runs the same examples on Nano Kit. The site showed none of them: the example pages offered React, Svelte and Next.js versions alone, and nothing told that the DevTools panel itself is built with the kit.
What
example-viewsync key, so a Nanoviews tab picked on one page stays picked on the others.@nano_kit/store, with its views written in Nanoviews.skills/nano-kit-store/DOCS.mdis regenerated for it.website/astro.config.js: the Umami script attributes lose the quotes thatstylistic-js/quote-propsflags since@trigen/oxlint-config11. The rootlintcovers./packages/*alone, so nothing caught it before.Notes
nanoviews,@nanoviews/routerand@nano_kit/*from npm, so their sandboxes install the published packages. The sandboxes were not opened in a browser.skills-docs --checkpasses, and every new link answers 200.