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
Use Case
As an NLE TAMS plugin vendor, I'd like to present a useful list of Flows and Sources to the user. However returning them in an unstable order or sorting by pulling the entire list and then sorting clientside lead to inefficiency or bad user experience
Action
Write an ADR covering these broad options:
No sorting - all clientside
Sorting by any of the query string parameters already in the spec
Fixed default sort by most recent metadata_updated
Optional sort by metadata_updated
Draft the spec changes for one of the simple options
After some discussion, it seems option (2) is probably more complexity than we want, and fails "TAMS is not a MAM" as a principle. So option (3) or (4) probably make sense.
Activity
samdbmg commentedon Apr 29, 2026
After some discussion, it seems option (2) is probably more complexity than we want, and fails "TAMS is not a MAM" as a principle. So option (3) or (4) probably make sense.
samdbmg commentedon Jul 10, 2026
TSC 2026-07-10
There's now a draft ADR for approaches to this for us to decide on the preferred approach. Review comments very welcome on this one