[9.x] Proper fix when provided path is '0' #40050
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
|
i think this fix must be applied to other functions too such as: path, basePath, bootstrapPath, configPath..... |
|
As a reminder, I used |
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.
#40013 was incorrect, because when provided argument was '0',
we were appending
$path(i.e. '0') instead ofDIRECTORY_SEPARATOR.$path(i.e. '/0').To summarize the behavior after this PR:
'foo''/foo''0''/0'''(default)''In addition, as I'm using a loose comparison, it supports the following cases (they are not supported nor expected, though it doesn't harm to work better with them):
null''false''