refactor(scaffold): rename c-page-* to l-* and add p-* page styles - #881
Open
yusasa16 wants to merge 10 commits into
Open
refactor(scaffold): rename c-page-* to l-* and add p-* page styles#881yusasa16 wants to merge 10 commits into
yusasa16 wants to merge 10 commits into
Conversation
- Replace c-page-home/c-page-sub with l-home/l-sub for layout - Add p-home, p-sub-default, p-blog-index, p-form for page-specific styles - Replace c-content-index with c-categories component Made-with: Cursor
…ctor Made-with: Cursor
…ut-naming # Conflicts: # packages/@d-zero/create-frontend/index.spec.js
Collaborator
Author
|
リントエラー（ |
yusasa16
marked this pull request as ready for review
September 7, 2026 01:20
yusasa16
requested review from
YusukeHirao,
arktds,
dz-furukawa and
teppei-d
as code owners
September 7, 2026 01:20
…t-naming Resolve conflicts caused by the sample component cleanup on v6: - l-home.css, l-sub.css: keep l-* naming, drop nav-global/nav-sitemap/content-index rules - home.pug, sub.pug: keep l-* naming, drop the nav-global/nav-sitemap slots - 200/210_blog_index.pug: accept the deletion and drop the orphaned p-blog-index.css - style.css: keep the layout/page layers, follow the c-content-main and burger-editor moves - index.spec.js.snap: regenerate Note: scaffold markuplint still rejects l-*/p-* class names. Pending d-zero-dev/linters#847.
…ha.2 Pick up d-zero-dev/linters#847, which allows the l- and p- class name prefixes, so the l-*/p-* layout and page classes introduced in this branch now pass markuplint.
…rk around #1040 at-rule-prelude-no-invalid and declaration-property-value-no-unknown throw "Bad syntax reference" on valid CSS because css-tree is pinned to 3.1.0 while @csstools/css-syntax-patches-for-csstree resolves to 1.1.5. The exception is raised inside the rules, so stylelint-disable comments cannot avoid it. This is a temporary workaround for #1040. Drop these two lines once that issue is fixed.
…selector list
stylelint-config 6.0.0-alpha.2 surfaced a selector-nested-pattern error on
`* { &, &::before, &::after { ... } }` that the earlier css-tree crash had masked.
The compiled CSS is unchanged.
This is a temporary workaround: d-zero-dev/linters#862 fixes the rule to allow a bare `&`
in a selector list, so this can go back to the nested form once that lands in the 6.x line.
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
1 participant
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.
Summary