Fix collection breadcrumbs order on collections#2374
Merged
alecritson merged 2 commits into1.xfrom Jan 29, 2026
Merged
Conversation
glennjacobs
approved these changes
Dec 11, 2025
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
2 participants
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.
Currently breadcrumbs are ordered incorrectly for sub collections, take this tree for example:
If we go into the
Test B Child D Grandchild A Child Acollection, we see the breadcrumbs appear like so:Which is incorrect as
->ancestorswill just be ordering the records based on their default Laravel sorting, not the order they appear in the tree.This PR looks to solve this by introducing the nested set
defaultOrdersorting to the query, afterwards the result is: