9.0: BUGFIX: Fix default dimension resolving #4066
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
skurfuerst
commented
Mar 5, 2023
| $siteConfiguration['contentDimensions']['defaultDimensionSpacePoint'] ?? [] | ||
| ); | ||
| $siteConfiguration->defaultDimensionSpacePoint | ||
| );*/ |
There was a problem hiding this comment.
I have removed this, because we need a way to express "X cannot match..." -> need to discuss this. maybe extend the matching logic.
| UriConstraints $uriConstraints | ||
| ): UriConstraints { | ||
| $dimensionSpacePoint = $this->reduceDimensionSpacePointToConfiguredDimensions($dimensionSpacePoint); | ||
|
|
||
| if ($targetNode->getUriPath() === '' && $dimensionSpacePoint->hash === $this->defaultDimensionSpacePoint->hash) { |
There was a problem hiding this comment.
we need the target node, because UriConstraints does NOT contain the target URL...
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.
@bwaidelich we need to discuss this a bit further; some more edge cases appeared ;)