[v10.0.x] Nested folders: Fix folder hierarchy in folder responses #74581
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.
Backport 9fcee9b from #74516
What is this feature?
#66835 modified the folder DTO to include the folder parents (if nested folders are enabled) to be used by the frontend the show the full path to Folders in the breadcrumbs.
When I implemented it I had in mind that ancestors not visible to the user (due to permissions) would be included as is and the frontend would handle them.
In retrospect, I realise that this problematic therefore I have made this fix that redacts their UID and the title instead.
It also fixes another bug (wrong guardian used) and populates correctly the
canEdit
,canView
etc properties for ancestors.Why do we need this feature?
[Add a description of the problem the feature is trying to solve.]
Who is this feature for?
[Add information on what kind of user the feature is for.]
Which issue(s) does this PR fix?:
Fixes #
Special notes for your reviewer:
Please check that: