-
-
Notifications
You must be signed in to change notification settings - Fork 627
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
[NEXT] fix: changed the islocalPath conditions to more effective #999
Closed
Conversation
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
@anikethsaha Please review the following output log for errors:
See complete report here. |
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.
What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
Yes #984
If relevant, did you update the documentation?
NA
Summary
The current conditions in the
islocalPath
method are not so effective because of two reason/^\./.test(str)
is checking for the string format whether its starting with.
or. It will produce the wrong output if any wrong path is passed with correct path format eg -../not-A-Valid-Path
will be true so the method will return true -- need to remove it (removing seems fair than adding more regex char)isAbsolute
it wont check for a valid path but for a format of the string. it can be added withexistsSync
usingand
conditionDoes this PR introduce a breaking change?
May be not sure
Other information
tests in #984 will pass if with respect to this changes