-
Notifications
You must be signed in to change notification settings - Fork 10
feat: Add API for cleanly retrieving the capture group matches within a LogEvent's Token; Use the API in LogEventView::get_logtype to correctly only substitute leaf capture group matches.
#205
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
7 commits
Select commit
Hold shift + click to select a range
aaa71b8
Add ystdlib.
davidlion 2dd7d68
feat: Add API for cleanly retrieving the capture group matches within…
davidlion b7375f2
Add unit tests; fix api; fix logtype.
davidlion d246407
Fix coderabbit comments.
davidlion 2ea69af
touchup readme
davidlion c3acb2e
Tweak error handling.
davidlion 0641f76
Address review comments.
davidlion 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
This case is never currently reached right? Even if it was reachable, It seems like for it to be reached something has to be broken, but currently the code will just continue treating it as a non-capture var.
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.
Ya currently
get_capture_positioncan only returnNoCaptureGroupMatch, but this error handling is more future proof since any other error should causeget_capture_matchesto fail.Inside log surgeon
get_capture_matchesis only used inget_logtypewhich doesn't handle any errors, but the clp code that usesget_capture_matcheswould error. We could makeget_logtypereturn aResultif we don't want it to always return something.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.
The main question is what should happen if
get_capture_matchesfails with any other type of error. In the case ofNoCaptureGroupMatchits clear that this is just a non-capture group, soget_logtypewill just treat it as a non-capture and continue. But, with other error types it'll do the same which is probably wrong.That being said, as of now the behavior is correct, so this could just be left as is and addressed in the future if a case does come up.