docs(intent): a posting's rule.match needs a literal that says something (#7180) - #242
Merged
Conversation
…ing (#7180) The value is rendered into the generated posting handler AS the authored literal, so a blank one looks up the empty string: no rule row matches, and the posting skips every source document to the unposted worklist with the intent, the generation and the publish all green. An empty or omitted match value is now refused when the intent is read, so the accident is named where it is authored. Co-Authored-By: Claude Opus 5 <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.
Companion to eclipse-dirigible/dirigible#7253.
rule.matchis documented as acolumn: literalselector, but nothing said the literal has to say something. It is matched against the rule row's own column as authored, so a blank one looks up the empty value: no rule row matches, and the posting then takes its documented "no rule row" path and skips every source document to the unposted worklist - with the intent, the generation and the publish all green, and nothing anywhere naming the cause.The platform now refuses an empty or omitted match value when the intent is read; this states the rule where the key is documented.
🤖 Generated with Claude Code