-
Notifications
You must be signed in to change notification settings - Fork 4
NEW @W-21600165@ - Add pattern_not_regex support to reduce false positives in custom rules #439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6960a75
Add pattern_not_regex support to reduce false positives in custom rules
aruntyagiTutu ea0fc59
pattern not regex feature in regex engine
aruntyagiTutu dd61be2
Merge branch 'dev' into arun.tyagi/add_pattern_not_regex_support
aruntyagiTutu 69e9b06
refactor: Rename pattern_not_regex to regex_ignore for clarity
aruntyagiTutu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
11 changes: 11 additions & 0 deletions
11
...lyzer-regex-engine/test/test-data/patternNotRegex/emailHeaders_WithUnsanitizedPayload.dwl
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| %dw 2.0 | ||
| output application/java | ||
| --- | ||
| { | ||
| headers: { | ||
| To: $(payload.recipientEmail), | ||
| Subject: $(payload.subject), | ||
| From: $(payload.fromAddress) | ||
| }, | ||
| body: payload.message | ||
| } |
13 changes: 13 additions & 0 deletions
13
...ode-analyzer-regex-engine/test/test-data/patternNotRegex/emailHeaders_WithValidatedId.dwl
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| %dw 2.0 | ||
| output application/java | ||
| --- | ||
| { | ||
| headers: { | ||
| To: "customer@example.com", | ||
| Subject: "Property Update", | ||
| "In-Reply-To": $(validatedMessageId), | ||
| References: $(validatedMessageId), | ||
| From: "noreply@dreamhouse.com" | ||
| }, | ||
| body: payload.message | ||
| } |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens if an invalid regex is passed does that validation happen before this ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
**Yes, validation happens before this code executes.
In config.ts (lines 82-84), regex_ignore is validated during configuration parsing:
const rawPatternNotRegex: string | undefined = ruleExtractor.extractString('regex_ignore');
const patternNotRegexString: string | undefined = rawPatternNotRegex
? validateRegexString(rawPatternNotRegex, ruleExtractor.getFieldPath('regex_ignore'))
: undefined;
The validateRegexString() function tests if the pattern is a valid regex and throws a descriptive error if it's invalid. This happens during config loading, before any engine execution.
So by the time engine.ts calls convertToRegex(), the regex pattern has already been validated and is guaranteed to be valid (or the engine wouldn't have started).
Flow:
**