You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The chapter overview should obviously be more informative than the current status. It would be nice, if the card would show the user a quick overview on the current state of the chapter and ideally this overview is role dependent (see the mockup description on the right).
The idea would be to have multiple sections within each card, the first section would list for each root component type of this chapter the total number of occurrences in the chapter, ideally grouped by status as shown in the mockup.
In the second section the translation progress for each language could get rendered for example.
I guess it probably makes sense to make an encapsulated component for each section and then have a query for each card (even if this is not very efficient as we won't have that many chapters).
To get the list of component types per chapter with the associated counts, the api_componenttype type could be queried with its 1:n relation to api_component and filter by chapter (directly via GraphQL).
For the grouping by status, I think this a bit more tricky since the status needs to get calculated for the whole tree and
therefore I guess it makes sense to add a database view for this functionality. I would therefore suggest to ignore the grouping by status for now and just render the total count per component type....
The text was updated successfully, but these errors were encountered:
Goal
The chapter overview should obviously be more informative than the current status. It would be nice, if the card would show the user a quick overview on the current state of the chapter and ideally this overview is role dependent (see the mockup description on the right).
The idea would be to have multiple sections within each card, the first section would list for each root component type of this chapter the total number of occurrences in the chapter, ideally grouped by status as shown in the mockup.
In the second section the translation progress for each language could get rendered for example.
Mockups
https://drive.google.com/drive/u/0/folders/1WIyKWdV41zwW5ijMIv5brCX-dheqHQWw
Ideas for an approach
I guess it probably makes sense to make an encapsulated component for each section and then have a query for each card (even if this is not very efficient as we won't have that many chapters).
To get the list of component types per chapter with the associated counts, the
api_componenttype
type could be queried with its 1:n relation toapi_component
and filter by chapter (directly via GraphQL).For the grouping by status, I think this a bit more tricky since the status needs to get calculated for the whole tree and
therefore I guess it makes sense to add a database view for this functionality. I would therefore suggest to ignore the grouping by status for now and just render the total count per component type....
The text was updated successfully, but these errors were encountered: