-
Notifications
You must be signed in to change notification settings - Fork 164
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
TabularInline: use one row per object (instead of two) to facilitate sorting #683
Comments
The reason why I put title to separate line was because of long titles. Sometimes when the title is really long it completely expanded the size of first column. Which third party plugin are you using for sorting? |
For example, this plugin: https://github.com/matthiask/django-admin-ordering I just tried native Django and a very long title. The approach Django uses to handle this is:
|
Yeah, I see it now. If you can draft a PR, I will be happy to review it. Regarding sorting functionality, I will try to take a look and prepare built-in MVP directly in Unfold without any third party dependencies. |
@marcpicaud are you willing to take a look on it and draft a PR fixing multiple rows per one record? |
@lukasvinclav |
Is it a third party application feature request?
No
Describe your feature request
Unfold's TabularInline template creates 2 rows per object (1 for the name, 1 for the fields) :
Django's TabularInline creates 1 row per object
This is not really a bug per se, but all 3rd party plugins offering a sortable functionality are expecting 1 row per object, and thus they are not compatible with Unfold. Wouldn't it be better to stick with native Django's structure ?
Possible solutions
Let me know what you think, I could draft a PR for either
The text was updated successfully, but these errors were encountered: