Filter outdated but not deleted baskets from REST endpoints
Summary
Basket's REST API returns 404 for outdated baskets - not a problem in general.
But!
When querying the foodsaver's baskets, the outdated baskets still get returned - without any chance to see if one is outdated. The only way to get the until-timestamp information is via the now 404 returning endpoint mentioned above...
Steps to reproduce
Fetch API endpoints mentioned above ( /api/baskets?type=mine
| /api/baskets/{id}
)
What is the current bug behavior?
No logical way to access/know the until-timestamp of a foodsaver's own baskets.
What is the expected correct behavior?
Either return basket with designated status instead of 404 (recommended by me) - or don't return it on /api/baskets?mine
after until
time is reached.
Relevant error messages and/or screenshots
Possible fixes
Edited by David