fix regex too complicated error in developer edition#313
Merged
pozil merged 2 commits intoMay 25, 2022
Conversation
|
Thanks for the contribution! Before we can merge this, we need @exiahuang to sign the Salesforce.com Contributor License Agreement. |
Contributor
|
@exiahuang - Thanks for this PR. Your solution is elegant and I like the guard/continue pattern. It does not, however, follow our style conventions in this Repo. Can you please tweak to include {}'s around the continue statement. I know it's not technically required by Apex, but it is how the rest of the Repo is done. |
Contributor
Author
|
@codefriar Thank you for for comment. I have fix it. Please check it again. |
msrivastav13
approved these changes
May 25, 2022
Contributor
|
Thank you @codefriar and @exiahuang |
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
4 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.
What does this PR do?
Fix
Regex too complicatederror in developer editionWhat issues does this PR fix or reference?
#312
The PR fulfills these requirements:
[x] Tests for the proposed changes have been added/updated.
[x] Code linting and formatting was performed.
Functionality Before
Regex too complicated Error.
Functionality After
Fix the error in DE.