Repository navigation
Detail the navigation query change in the 26.1 migration notes - #294
Merged
Merged
Conversation
Test Results0 tests 0 ✅ 0s ⏱️ Results for commit c7df5fc. ♻️ This comment has been updated with latest results. |
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
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.
The migration note "Custom navigation queries need to be adjusted manually." in the Corporate Memory 26.1.3 release notes did not say what has to be adjusted.
Wording based on a description from development.
Open follow-up: the repository has no page documenting the
navigation.topQuery/navigation.subQueryconfiguration, so there is nowhere to link readers for the new query contract and no example of the new edge-listing shape.🤖 Generated with Claude Code
https://claude.ai/code/session_01RNCZszS2kCnizuV9aYPJ1x