-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
Move relations into the content-manager main-view and improve loading performance #14401
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
Conversation
Codecov ReportBase: 58.79% // Head: 58.72% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #14401 +/- ##
==========================================
- Coverage 58.79% 58.72% -0.07%
==========================================
Files 1327 1340 +13
Lines 32114 32500 +386
Branches 6007 6143 +136
==========================================
+ Hits 18881 19086 +205
- Misses 11371 11525 +154
- Partials 1862 1889 +27
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
…Relations are called for non compatible relations
…lly-fail-no-search-results
…o-search-results fix: gracefully fail 404 results from API
…-param CM: Stop passing defaultParams down (not needed any longer)
|
@pwizla @meganelacheny Quick heads up: we are going to merge this PR into |
feat: re-add the count & make it dynamic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Thanks for the heads-up @gu-stav. I'll have a look at it Monday to make sure screenshots and everything (already published on docs-next) are up-to-date. 🙌 |
|
This pull request has been mentioned on Strapi Community Forum. There might be relevant details there: |
What does it do?
This summary moves relational fields from the sidebar into the main view of the content-manager. Fields can now be resized as any other field, which should give content-editors more a better editing experience.
It improves the overall performance for applications with a large number of relations, because now the connected entities are lazily loaded instead of being part of the initial (internal) content API response.
Screenshots
Why is it needed?
Before relations were quite limited in space and we had numerous issues about loading performance.
How to test it?
This PR will be released as an alpha version. Details will follow.
Related issue(s)/PR(s)