chore(core): remove obsolete regex based matching TODO - #2837
Open
KushagraB424 wants to merge 2 commits into
Open
KushagraB424 wants to merge 2 commits into
KushagraB424 wants to merge 2 commits into
Conversation
KushagraB424
requested review from
Aryan-sharma11,
AryanBakliwal and
achrefbensaad
as code owners
August 5, 2026 18:29
KushagraB424
force-pushed
the
chore/remove-obsolete-regex-todo
branch
from
August 5, 2026 18:30
d55cef5 to
9656f19
Compare
Aryan-sharma11
approved these changes
Aug 9, 2026
Member
There was a problem hiding this comment.
let's revert this document.
Aryan-sharma11
self-requested a review
August 9, 2026 10:12
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
2 participants
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.
Purpose of PR?:
Removing an obsolete developer
TODOcomment fromunorchestratedUpdates.gowhere regex-based matching is actually already implemented.Fixes #2836
Does this PR introduce a breaking change?
No.
If the changes in this PR are manually verified, list down the scenarios covered::
N/A (only removing a comment).
Additional information for reviewer? :
N/A
Checklist:
<type>(<scope>): <subject>