Dependency injection: fix Loader_Pass
being broken on Windows
#20503
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.
Context
Summary
This PR can be summarized in the following changelog entry:
Relevant technical choices:
Follow up on #20074, which changed the
Loader_Pass
class to compare paths against (other) paths with hard-coded forward slashes.This silently broke the Dependency injection layer for anyone compiling on Windows, i.e. the DI container scripts would run without errors, but once the DI container is attempted to be used, everything breaks.
This commit should fix that in a similar way as a previous similar issue was fixed in another part of the DI container setup (PR #16364).
Test instructions
Test instructions for the acceptance test before the PR gets merged
This PR can be acceptance tested by following these steps:
Easiest way to reproduce the original issue is as follows:
0. On a Windows computer....
trunk
.composer install
- the DI container will appear to be build without errors.vendor/bin/phpunit -c phpunit-integration.xml.dist
and see it fail in the bootstrap before the test run even gets started.Rinse & repeat with this branch & see things working again.
Recommendation: also test this PR on Mac and Linux just to make sure there is no regression on that side of things.
Test instructions for QA when the code is in the RC
QA can test this PR by following these steps:
Impact check
This PR affects the following parts of the plugin, which may require extra testing:
UI changes
Other environments
[shopify-seo]
, added test instructions for Shopify and attached theShopify
label to this PR.Documentation
Quality assurance
Innovation
innovation
label.Fixes #