Fixed regex pattern used for annotations in OEM extensions#519
Open
Fixed regex pattern used for annotations in OEM extensions#519
Conversation
Signed-off-by: Mike Raineri <michael.raineri@dell.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
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.
Someone internal showed me the output of an inserted OEM extension and the resultant pattern was not aligned with the annotations pattern we use elsewhere.
This was showing up in the final yaml output at the end of the toolchain:
The extra slash after Message results in it searching for a slash followed by any character, when the intent is to escape the . character to indicate we're searching for a . character.
The intended output should be: