- Issue created by @chrisck
anish.ir → made their first commit to this issue’s fork.
- 🇷🇴Romania amateescu
I agree that having this feature would be super useful. I'd like to see it implemented in a very specific way if possible, by creating "on-demand" custom views for each trashable entity type. The reason for them being custom is that we need to display different fields than
/admin/content
for example. Hey @amateescu,
I’ve attached a screenshot showcasing the functionality I’ve implemented so far. Please have a look and let me know your feedback.
I also need some clarification regarding the "on-demand custom view" you mentioned. Are you suggesting:
- Should each trashable entity type have its own predefined View, or should we generate Views dynamically based on the selected entity type?
- When you say "on-demand," do you mean the Views should be created programmatically when accessed, or should they be predefined and stored permanently?
- Are there specific fields you'd like displayed for different entity types, or should the View dynamically adjust based on available fields?
- Or did you have something else in mind?
Let me know your thoughts! Thanks.
- 🇷🇴Romania amateescu
Re #6:
Should each trashable entity type have its own predefined View, or should we generate Views dynamically based on the selected entity type?
Generate Views dynamically based on the selected entity type.
When you say "on-demand," do you mean the Views should be created programmatically when accessed, or should they be predefined and stored permanently?
Views should be created programmatically when accessed.
Are there specific fields you'd like displayed for different entity types, or should the View dynamically adjust based on available fields?
The View dynamically adjust based on available fields, using the list of fields we currently display in the trash controller.
- 🇮🇳India Vivek Panicker Kolkata
As anish.ir has not worked on this issue for quite some time, unassigning the issue from him.