{{ message }}
feat: add omitted frontmatter key to suppress expected-missing lint warnings#113
Open
mvanhorn wants to merge 1 commit into
Open
Conversation
rajpratham1
approved these changes
Jun 25, 2026
rajpratham1
left a comment
rajpratham1
left a comment
There was a problem hiding this comment.
This is a well-designed feature that adds support for an omitted frontmatter key to explicitly suppress expected "missing section" lint warnings. The implementation is consistent across the parser, model, and linting layers, and it's backed by thorough test coverage covering parsing, case-insensitive matching, filtering invalid values, and rule behavior.
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
2 participants
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
Adds an
omittedfrontmatter key so an author can declare that a section (for examplecomponentsorspacing) is intentionally absent. Declared omissions suppress the matchingmissing-sectionswarnings while leavingbroken-refand naming-convention rules untouched.Why this matters
Today a clean design file with no
componentssection produces the same warning as one that forgot it, so "intentionally omitted" and "linter didn't notice" look identical to a reviewer. Theomittedkey makes the intent explicit: a declared omission emits aninfo-level acknowledgement instead of a warning, and the rule still fires for sections that are absent without being declared. The maintainer called this "a good idea" in #78; the change is purely additive, so files without the key behave exactly as before.Testing
Added tests across the parser, model, and the two missing-section rules covering declared omissions, undeclared absences, and that
broken-refis still reported. The existing suite passes.Closes #78