Uh oh!
There was an error while loading. Please reload this page.
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.
[/codebase-design]
extractNestedYAMLScalarcompiles up to 3 regexps on every invocation — once per candidate line inside the parent block. Since the patterns depend only onescapedChild, which is fixed for the whole scan, they can be compiled once and reused. This refactor is the ideal seam to make the helper deeper.💡 Suggested refactor: compile once, match many
Build the matchers once in the caller, then pass them in:
@copilot please address 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.
Done. The three scalar patterns are now compiled once per scan in
buildNestedYAMLScalarMatchers(escapedChild)andextractNestedYAMLScalarjust iterates the prepared matchers, so no regexp compilation happens per candidate line.