runverzagt
commented
9 years ago The more I think about it, it we want to us OOP semantics, we should have a class Beer which has methods to create and retrieve it. Is this in line with the Flask semantics? I could see that each class is supposed to represent an api command, but that seems a little ridiculous, and certainly not the pythonic way of doing things.
I didn't realize this wasn't already being addressed, but there should be a way to make a query for information on a random beer.
I don't think authentication should be necessary for the ability to view the database, and that's all that would be required for this. If the user is registered then they can have the option to add it to their list but I don't see why that should be required for read-only operations.