Fix alias fields not showing up in permissions #11685
Merged
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.
Fixes #11683
Bug
With the following data model as example:
Alias fields like Notice aren't showing up in Field permissions, hence the admin is unable to grant read permission to the restricted users/roles:
Investigation
#11265 extracted
getFieldsForCollectionSorted
as a function, but the second.filter()
here shouldn't be present as that should only be applicable inuse-field-tree
to hide groups/aliases from the Filter input.directus/app/src/stores/fields.ts
Lines 270 to 276 in aa0c7c7
After fix applied