Support meal preference priority

[ipwnponies]

In IRL, if a meal is unavailable, the user decides on their second choice. Many users will probably have a common fallback. We should support this by accepting a ranked preference of meals/restaurants. The retry logic will need to understand when a meal is sold out (vs. a http timeout) and to attempt to reserve the next choice.

[edmundmok]

As we go into more complex use cases like these, I think having some kind of more interactive user interface (e.g. web frontend) would be easier to use than through a CLI, i.e. something like an offline version of Mealpal's map interface. Images (crucial in choosing my preferences!) in particular will be wasted through CLI, especially if we want to list restaurants, meals, etc.

We can consider moving this v2 into a new project instead, which can support less technical users.

[ipwnponies]

My opinion is for this tool to remain a CLI/scheduled task. The main use case is to automatically reserve a meal, so we don't need to remember to do so, especially if we know what we already want. Meal priority is for "error handling", listing meals( #7) are quality-of-life improvements to maintain our sanity (reading json blobs).

The UX you've suggesting starts to out-run the usefulness of the tool: you only need to use these extra features (very rarely) to initially setup preferences/scheduler. But probably very costly to set something slick up for non-technical user.

[edmundmok]

Good points, let's keep this CLI only then.