Luke Heath

Results 251 comments of Luke Heath

@chiiph Happy to take it on. I've re-spec'd and brought it back to Ready.

@fx5 Sorry about that, the specs were unclear. Currently, no body returns a 500. Instead, we'd like to return a 400 (Bad Request) so that the frontend will simply display...

And I've updated the specs to hopefully be more clear. Let me know if you have any questions. Thanks!

@fx5 Unfortunately it looks like there were some spec changes that were not applied to the related issue (#7588). Instead of having a new URL param called `missing_10_days` we actually...

@mna I'm co-assigning this ticket to you to begin assisting with research and specifications for the epic. This is going to be a pretty substantial change. Before we take it...

@mna Thanks for your feedback! Based on your feedback, as well as the team's conversation during estimation, we are all in agreement that the best path forward is to include...

Martin: For implementation, it would be best to leave the current `packs` and `schedules` endpoints in place and focus on adding functionality to the queries endpoints. Then, once we have...

@mna After speaking with Mike and Zach, we have the 👍 on including this in v5 with breaking changes.

> This is not true anymore, now that we're doing this as a v5 breaking change, right? @mna Correct. The API will not be backward compatible. Migrations only need to...

@fx5 I am assigning this ticket to you to complete the specification process and bring to the estimation column. Our goal is to bring this ticket into the next release...