This release implements a read API, fixes some bugs, and does other small general improvements
In this release:
- Fixed an issue where analytics on the admin page were counting failed bot scraping requests
- Updated dependencies, most notably Django, fixing a few GitHub security advisories
- Moved the years arrays to all live in
settings.py, to simplify the process of setting up a new season - Made choices in pit and match scouting use a tuple, so that the display name can be translated correctly
- Created a custom
createsuperusermanagement command replacing the default Django one. This simplifies setting up a server for the first time, so admins don't have to manually create a profile and settings model for that initial user - Implemented a read API
- Users can create an API key on their profile page, after registering an account
- This allows access to match, event, and pit scouting data, as well as some convince routes for getting counts and what teams have data
- This API will allow third party developers and teams be able to run their own custom analysis on gathered data, make pit dashboards for displaying what data has been gathered, and if they want a programmatic way to import or export gathered data
- An auto-generated docs page aids in the usage of this API, it's available at
/apion the server - The API has support for pagination
- Updated the create custom event dialog, to better fit the style and behavior of the rest of the UI
Issues closed:
- #116 - Admin page analytics count failed bot requests as page visists
- #118 - Move the year arrays to be in settings.py
- #112 - In season fields, make the choice field use a tuple for each choice
- #119 - Create a custom createsuperuser management command
- #103 - Add an API
- #111 - Update the create custom event dialog