-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify sorting for relational fields in the Content Manager list view #2224
Conversation
Because higher in that note it is said that “Only one field can be displayed per relational field.”
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Hi @gurdiga! Thank you for submitting this PR. Could you please elaborate on why you think this change is necessary and what you are trying to achieve? I double-checked with engineers and what is currently described is expected, so at least this line shouldn't be changed in the documentation. Here's a screenshot of what works: Or maybe is there another part of the documentation that you would like to be improved? 🤔 |
Here is the place in documentation that I’m referring to: ![]() This Note refers to “Relational fields”, first some specificities, then some limitations. The first limitation says:
…which seems to imply that there can be relational fields which display several fields, while the first specificity says they can’t. Maybe I’m misreading it. 🤔 |
Hmm I see. This is not entirely clear for me either to be honest, so I'll dig deeper, test things further, and come back to you a.s.a.p. |
(still trying to figure out how it works and reproducing it, I'll keep you posted next week) |
Finally getting back to you. I can't figure out why the "Sorting cannot be enabled for relational fields which display several fields." was written in the first place. It doesn't seem like it works this way, in Strapi 5 at least. However, updating docs as you suggest would also be wrong because you can sort by relational fields, as shown in the screenshot. So I think the docs should be updated as I suggest in my comments, actually deleting the first limitation entirely and rewriting the sentences above to simplify this. Would that be OK for you? |
docusaurus/docs/user-docs/content-manager/configuring-view-of-content-type.md
Outdated
Show resolved
Hide resolved
docusaurus/docs/user-docs/content-manager/configuring-view-of-content-type.md
Outdated
Show resolved
Hide resolved
docusaurus/docs/user-docs/content-manager/configuring-view-of-content-type.md
Outdated
Show resolved
Hide resolved
Sure! I hope I got it right this time. PS: Thank you for the hand-holding. 🙂 |
Much welcome, @gurdiga! The PR is now approved, merged, should be live on docs.strapi.io in a few minutes, and will be mentioned in the next weekly snapshot release. |
What does it do?
Removes a few words that seem to cause confusion.
Why is it needed?
Because higher in that note it is said that “Only one field can be displayed per relational field.”
Related issue(s)/PR(s)
None.