Best practice for implementing list/detail views for complex structures

[nareshbhatia]

I am building a list/detail view for a complex alerting system. Items in the AlertList must show high level summaries of alerts. When an item in the list is clicked, the detail view must show all the details of the alert.

Since the Alert object is very complex, the query to fetch the AlertList is fairly deep. It must reach out to different attributes of different alert types to create a summary. In such cases, is it a good practice to create a new GraphQL type called AlertSummary which is computed by the server just to make displaying the AlertList easier. AlertSummary will essentially be a subset of the the full Alert entity. Is this a good practice? Is there a good example that I can refer to?