plutone11011 / gamereqsapi Goto Github PK

We should add a developer string field as a possible query parameter, and return results that match it, in a similar way to the name property.

3 steps:

1. in get_game, we need to initialize a new variable developer the same way name is initialized, and pass it as a keyword argument to both db calls to game_query
2. then in QueryBuilder, add a new method that builds the developer filter the same way name_query does
3. finally in the db module, add a new property to the query_functions dictionary: the key must have the same name as the one passed through kwargs in the view function, and the value must be the name of the method created in QueryBuilder

This API lacks a mechanism for authentication

The current homepage shows a wrong heading and paragraph. The heading should be centered, and should contain Game requirements API instead.
The paragraph should also be centered, and contain A prototype API to visualize games' system requirements from Steam

You may use a template, in which case create a folder named template

In the get_game view, replace the call to flask abort with a more meaningful message, like Games have no resource called (parameter_name).
Look at update_game and delete_game for how to handle the return message statement (when rowcount is None, not on exception).

Querying /games endpoint gives the right ids, but querying /games/info, /games/minimum_requirements and /games/recommended_requirements only return null ids.

Query creation is starting to get messy, so there is the need to refactor query functions in db.py to make it more readable and easier to add new filters. Might use PyPika.
Working on query-refactor branch