At the moment, the /v1/specs API will respond with an array of job specs, which are sorted based on how they happened to be loaded from the filesystem (see: code). They should be sorted according to what an API client would realistically expect.
I expect a client would want the results they get to be:
Based on the query, if there is one
Alphabetically sorted on the name field otherwise
In particular, this change will improve user experience in the downstream UI when rendering larger lists of job specs.
At the moment, the
/v1/specsAPI will respond with an array of job specs, which are sorted based on how they happened to be loaded from the filesystem (see: code). They should be sorted according to what an API client would realistically expect.I expect a client would want the results they get to be:
namefield otherwiseIn particular, this change will improve user experience in the downstream UI when rendering larger lists of job specs.