Repository navigation
lint: duplicate_business_key for pages sharing a frontmatter ticket - #1472
Draft
belchiordameao-cmd wants to merge 1 commit into
Draft
belchiordameao-cmd wants to merge 1 commit into
belchiordameao-cmd wants to merge 1 commit into
Conversation
…s_key) Refs akitaonrails#1471 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Refs #1471.
Adds a zero-LLM lint rule,
duplicate_business_key. Two or more live pages whose frontmatter has the sameticketvalue (a string, or an array of strings) produce onewarningfinding that lists every such page. Blank ids are ignored, and matching ignores case and surrounding whitespace.Why: in a field store, 33 external ticket ids each appeared on 2+ live pages. Those pages recorded the same decision twice in wording too different for the
duplicate-title check, or for any similarity threshold, to pair them. A shared business key catches them reliably.rule_based_findingsonly; no schema or migration change, and nothing is deleted or merged. Like the other rule-based findings, it is advisory.rule_pass_flags_duplicate_business_key, covering a string vs. an array that share an id, plus a blank id that must not count.Not built locally (no Rust toolchain on the machine I prepared this on), so I'm relying on CI. Happy to rename the field or make it configurable through
LintOptionsif you prefer.🤖 Generated with Claude Code