-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: error from executing url regex #559
Merged
joelbettner
merged 6 commits into
Expensify:main
from
eh2077:21266-try-catch-regex-execution-error
Jul 27, 2023
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
62d336d
try/catch error from executing url regex
eh2077 6c4a3d1
add test for try/catch change for methods
eh2077 9ac15b6
Log warning message for regex execution errors
eh2077 42c1842
fix lint
eh2077 fbe2ee8
improve error log message
eh2077 6efa019
use console.warn to log error message
eh2077 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
Instead of undefined, lets return
[]
as it was doing previously?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.
@allroundexperts I tend to stick with return
undefined
when exception occurs for the following reason. This method currently is only used by methodgetRemovedMarkdownLinks
which needs to call this method twice to do diff to get the removed links. My point here is to let methodgetRemovedMarkdownLinks
return empty array[]
if any of the two links array isundefined
, which means don't remove links if any exception occurs. Does it make sense to you?Let's say, there's a new comment with multiple links but one of them causes regex execution error, in this case, we return
undefined
to skip removing any links. If we return[]
for the new comment, then methodgetRemovedMarkdownLinks
will remove all links.