Repository navigation
docs: delete stale duplicate Imports API page - #318
Merged
Merged
Conversation
Remove apps/docs/content/docs/02.api/13.imports.md, the stale Imports page that described the old per-file "own instance / import from 'styleframe'" model. The authoritative single-instance page (14.imports.md) already covers every still-correct topic. This also resolves the 13. numeric-prefix collision with 13.merging.md and leaves exactly one Imports entry in the API nav. The published /docs/api/imports URL is preserved (both files mapped to it), so no route 404s. SF-31
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This branch was successfully deployed
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
Delete the stale duplicate Imports API page (
apps/docs/content/docs/02.api/13.imports.md), leaving a single authoritative Imports page.Why
The API section had two pages titled "Imports". The removed
13.imports.mddescribed the old model — each*.styleframe.tsfile creates its ownstyleframe()instance and imports from'styleframe'. That contradicts the current single-instance architecture: the plugin'sgenerateExtensionModulereturns the config directly (tooling/plugin/src/plugin/generate/extension-module.ts:11-13), sostyleframe()inside an extension file hands back the same instance. The surviving14.imports.mddocuments this correctly and already covers every still-correct topic (consuming styles, exports, framework usage, HMR, all nine bundlers), so nothing needed folding — folding the old page's content would reintroduce the drift.Deleting the stale page also clears the
13.numeric-prefix collision it had with13.merging.md; the remaining files (12.composables,13.merging,14.imports) each have a unique prefix, which restores the ordering PR #132 intended. Implements SF-31.How verified
Content DB after the change (
.data/content/contents.sqlite,_content_docs_api):Exactly one Imports entry now, down from two.
Notes
/docs/api/imports(numeric prefixes are stripped from routes). Deleting the stale page leaves the authoritative page serving that exact URL, so the previously published URL does not 404 — a redirect would target itself and break the page. No internal docs link references the route, so none breaks.@styleframe/docsis in the changesets ignore list).