feat: create injectable regex utility function #536
Merged
Conversation
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
github-actions
bot
added
t-core-services
jirimoravcik
approved these changes
Sep 11, 2025
fnesveda
approved these changes
Sep 12, 2025
tobice
added
the
validated
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.
This PR introduces a new utility function,
createInjectableRegExp(), that converts any regex into an "injectable" version by removing its leading^and trailing$anchors.This is useful when you need to embed an existing pattern, which was originally designed to match a whole string, inside another regex to match it as a substring.
Thanks to this, we can replace APIFY_PROXY_VALUE_REGEX with REGEX_STR_USERNAME_VALUE in Apify proxy and solve this issue https://github.com/apify/apify-proxy/issues/1079.
The function was created in Apify shared repo, so it can be used in other places.