Open ipwnponies opened 5 years ago
To add on to the caching of meals, here are some relevant thoughts:
By the way, it seems like I can still access the API with an account that is no longer subscribed (though I probably can't order anything), so I can try to help out with some of these issues.
For v1, we can simply be naive and cache the last meal. For v2, we can cache meals per day of week.
Preference ranking with fallback behaviour is a great feature and enough work to warrant its own ticket (#9)
By the way, it seems like I can still access the API with an account that is no longer subscribed (though I probably can't order anything), so I can try to help out with some of these issues.
lol today was actually my last meal on the plan (putting it on hold for the next several weeks). So I was frantically dumping all the response for analyzing later. It's good to know that I can still use the api.
We can cache the response of the restaurant/meal/hours queries. This will provide users ability to lookup possible inputs to provide as arguments.
Meals might be trickier, since they can change day-to-day. That can be a follow-up to this ticket, the benefit of getting reasonable inputs to provide to CLI arguments is great enough on its own.