Document class design

[robsavoye]

There are many endpoints in the User stories, but they do break down into related groups of data queries., To avoid code duplication, a design document should identify base classes that can be shared by higher level classes. For example related queries about user statistics might have similar functionality, and should share code that uses arguments to the methods to change behavior. This will help determine the implementation of the data flow of the API, which is better to do now while the project is small and fluid. While currently the endpoints are relatively simple, there will be growing complexity as more endpoints get implemented.

[kshitijrajsharma]

Related to #7

[robsavoye]

Looking at the current code under the osmstats directory, I notice a lot of filters. Something to consider, is this generic functionality that should be in a base class ? This could force some refactoring of how the filters work.

[kshitijrajsharma]

Looking at the current code under the osmstats directory, I notice a lot of filters. Something to consider, is this generic functionality that should be in a base class ? This could force some refactoring of how the filters work.

@JorgeMartinezG