I noticed sortOrder defaults to asc globally. Would it be worth considering resource-specific defaults instead?
For security-related resources like product/component releases (often sorted by createdDate) or collections (sorted by version), consumers typically expect the most recent data first (newest-to-oldest).
If a universal asc default is preferred for simplicity, perhaps we could add a small note in the description to help set expectations for implementers/consumers.
Originally posted by @Mehrn0ush in #231 (comment)
I noticed sortOrder defaults to asc globally. Would it be worth considering resource-specific defaults instead?
For security-related resources like product/component releases (often sorted by createdDate) or collections (sorted by version), consumers typically expect the most recent data first (newest-to-oldest).
If a universal asc default is preferred for simplicity, perhaps we could add a small note in the description to help set expectations for implementers/consumers.
Originally posted by @Mehrn0ush in #231 (comment)