Describe the bug
The documentation for GET /flows/<flowid>/segments doesn't explicitly say that segments should be returned in time order, but implies it by the existence of ?reverse_order
Expected behavior
While most practical implementations return the segments in time order, many players/readers rely on being able to assume the list is sorted, so it should be called out explicitly.
Suggested fix
Call out explicitly that the results should be sorted in order
Additional context
Found as part of google/virtual-broadcast-production-assistant#314
Describe the bug
The documentation for
GET /flows/<flowid>/segmentsdoesn't explicitly say that segments should be returned in time order, but implies it by the existence of?reverse_orderExpected behavior
While most practical implementations return the segments in time order, many players/readers rely on being able to assume the list is sorted, so it should be called out explicitly.
Suggested fix
Call out explicitly that the results should be sorted in order
Additional context
Found as part of google/virtual-broadcast-production-assistant#314