All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
2.0.0 - 2019-04-03
- API documentation
- Data persistence to Database
- Candidates, Votes, Petitions and results endpoints
- Migrated v1 endpoints to v2
- Support for api v1
1.18.0 - 2019-04.0
- Create petition endpoint
1.17.0 - 2019-04-01
- View office results endpoint
1.16.1 - 2019-04-01
- Various Pylint errors
1.16.0 - 2019-03-31
- Create vote endpoint
1.15.2 - 2019-03-29
- Candidates registration where party and office did not exist.
- Candidate registration time response to local time
1.15.1 - 2019-03-28
- Previous behavior where candidates were registered more than once for an office.
1.15.0 - 2019-03-28
- Cnadidates registration for office endpoint.
1.14.2 - 2019-03-27
- Updates to the README and CHANGELOG files.
1.14.1 - 2019-03-26
- Unused imports in code
1.14.0 - 2019-03-26
- Version 2 of get all offices api route
- Offices are queried from a database
1.13.0 - 2019-03-26
- Version 2 of get office api route
- Authorization for get office/offices route
- Office is queried from a database
- Offices api requires authorization token
- Office json response now includes the office id
- Get office api route takes in integer as variable instead of uuid
1.12.0 - 2019-03-26
- Version 2 of Create office api route
- Authorization for create office route
- Office created is saved to a database
- Creating an office requires admin authorization token
- Office name and office type are saved as lowercase by default
- version 1 of offices api routes
1.11.0 - 2019-03-25
- Version 2 of delete party api route
- Authorization for delete party
- Party deleted is from a database
- Deleting a party requires admin authorization token
- Party id takes in integer instead of uuid variable
1.10.0 - 2019-03-25
- Version 2 of edit party name api route
- Authorization for edit party name
- Party name edited is from a database
- Editing party name requires admin authorization token
- Party id takes in integer instead of uuid variable
1.9.0 - 2019-03-25
- Version 2 of get parties api route
- Parties list is queried from database
- Party schema json response is ordered as per the schema fields
1.8.0 - 2019-03-24
- Version 2 of get party api route
- Authorization get parties api route
- Parties list is queried from a database
- Getting party/parties requires authorization
- Party id takes in integer instead of uuid variable
1.7.0 - 2019-03-23
- Logo field attribute to parties details
- Version 2 of create party api route
- Authorization for parties v2 api
- Parties to be stored in database
- To create a party it requires an admin user token
- version 1 of parties api routes
- Party id generated using uuid
1.6.0 - 2019-03-17
- Updated the CHANGELOG
- Updated the README
1.5.1 - 2019-03-17
- Removed unused imports on modules
- Unnecessary blank lines
- Code line length
- Whitespaces in modules.
1.5.0 - 2019-03-16
- Decorators to verify currently logged in user privileges
- Restrict access of route to specific class of users (normal or admin)
1.4.0 - 2019-03-15
- Logout route
- Blacklist table to store tokens when user logs out
1.3.1 - 2019-02-20
- Include PyJWT package in project requirements list
1.3.0 - 2019-02-20
- Jwt token encoding on user emails
- Jwt token decoding
- JSON response for user login and registration included token field.
1.2.0 - 2019-02-19
- User login endpoint route
- Validation for user login details
- Sanitized sql string queries
1.1.0 - 2019-02-16
- User registration endpoint
- Validation for user fields inputs
- PostgresSQL database connection
- default set passport Url on user registration
1.0.0 - 2019-02-12
- Offices endpoints.
- Parties endpoints.
- Validated data for user inputs.
- Heroku deployment for this release.