[5.x] Adjusts app extension namespace logic #11233
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
|
I think PR should be prioritised as it fixes this bug is affecting all Windows environments after the changes on 5.42 |
|
This PR fixes issue #11046 on Windows. |
|
Maybe this is the cause of #11241? |
|
Thanks! Got an alternative solution in #11246 |
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 fixes #11231
If the path contains backslashes, the nested directory handling introduced in #11046 will cause auto-loading to fail, even for classes that are not in sub-directories.
This PR refactors how namespaces are determined and adds some test coverage (just testing the namespaces produced from different base path and app namespace combinations).