v1.1.0

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 createsuperuser management 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 /api on 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

v1.0.1

This release fixes a bug introduced in the previous version

In this release:

• Removed the window reload added to fix the issue with favorite events working in production, as this caused page reload loops when Network-first service worker was enabled

Issues closed:

No issues closed for this release

v1.0.0

This is the first stable release of Open Scouting! Despite this being marked as stable, there will always be more bugs, most likely on devices I am not currently able to test on. Please open an issue if anything is found.

This release fixes the last several known bugs, and adds a few missing parts to internalization

In this release:

• Now when docker is built, it should correctly install gettext which is needed for translations
• Tests have been updated, as some were never updated for recent additions
• Added a dialog to send the user back home when loading pit scouting in demo mode, as demo mode in pit scouting doesn't work correctly
• Documented the needed translation strings when working with client systems
• If the contribute or pits pages are loaded without needed URL parameters, the user is now sent back to the index page
• Fixed an issue where favorite events weren't working in production. Now it's checked if that local setting isn't set up correctly, and automatically fixes it for the user
• Pit scouting questions are now translatable
• Adjusted the timing for boxes on the index page, to prevent strange "flickering" when elements were hiding and showing at the same time
• Fixed an issue where the team number on the contribute page was overwritten even if the team information box didn't find the team number for the robot to watch

Issues closed:

• #11 - Handle missing headers
• #56 - Demo pit scouting data is broken
• #108 - Favorite events not working in production
• #107 - Index page boxes transition at the same time
• #109 - Team information box on the contribute page overwrites team number if no valid team number is found
• #114 - Make pit scouting questions translatable

v0.1.11-alpha

This release of Open Scouting reorganizes templates in the codebase to help with organization and implements localization and translations. These are the last major changes to lead up to a stable release

In this release:

• Templates have been separated into multiple files, to keep the code more organized and to help with development
• Open Scouting now supports localization and internalization
  • Most strings are now translatable. Additionally, date formats and pluralization in some cases are also covered
  • A language switcher is available in the menu
  • Please see Contributing Translations if you're interested in adding translations in your language
  • This is still in a partially basic form, and some areas may need adjusted to support more languages. Additionally, right to left languages are not yet supported. Please open an issue if something doesn't seem to be working right
• Icons now have a margin instead of relying on spaces in templates

Issues closed:

• #100 - Reorganize templates
• #31 - Support multiple languages and localization

v0.1.10-alpha

This release implements a new notification system, updates the menu button to show any important warnings, updates some docs and fixes some style issues

In this release:

• The notification system has been redone
  • Notifications now appear at the top right of the screen and are queued, so multiple notifications can be shown at once and they won't get overwritten
  • Additionally, notifications can be shown with a type, which effects the color
• The menu button's icon and color now changes if there's any important messages to the user (reports need uploaded, low storage space)
• Buttons floating at the bottom of the screen are now slightly further away from the screen edges, to hopefully help with readability on mobile devices with rounded corners
• README updates with a new mobile image and better wording on features
• Other docs updates also include a new section on updating production installations

Issues closed:

• #34 - Add a notification queue
• #35 - Show indicators on the menu button if there's any important messages to the user
• #61 - Buttons aligned to the bottom of the screen clip into rounded corners of mobile devices
• #99 - Redo notification system

v0.1.9-alpha

This release adds a new admin dashboard, fixes some UX issues on the index page, and adds a terminal app for automating the creation of season_fields.py

In this release:

• Removed the data table page, as the advanced data view replaced it with more features
• Added buttons to go to the advanced data view page, on the event actions page and in the context menu on the contribute and pits pages
• Adjusted scrolling on the index page to no longer snap, so smaller screens can still use the page as intended
• Adjusted the size of links on the index page for smaller screens
• Added a basic admin dashboard
  • This dashboard allows admins to view all Data, Events, Users, and Pits on the server, and make changes to this data (as well as banning users) as needed
  • This data can be filtered to only show certain data
  • This dashboard allows for some bulk operations (deleting all data under an event) and isn't intended to be abused, only to allow for basic moderation and data modification as needed
  • Buttons have been added to the index page when an admin is logged in that quickly allows them to reach the admin dashboard
  • Additionally, basic, non-identifiable page view analytics are shown on the admin page
• Fixed an issue where load_settings() was called over and over again
• The client version is now shown in the menu
• A terminal app for creating new season fields has been developed and is available here
  • This app allows for season fields to be created and edited quickly, without needing to directly mess with any JSON

Issues closed:

• #97 - Remove the data table page
• #43 - Admin interface
• #98 - Adjust scrolling or content on the index page
• #57 - Create a script or UI for creating season_fields.py

v0.1.8-alpha

This release adds a user management system for handing user settings, adds a menu for managing device storage, and does various improvements to the event selector, including adding the ability to favorite events.

In this release:

• Changed the colors of true and false values in the advanced data view charts, so now it's easier to quickly digest the info on the capabilities page
• Made certain development instructions clearer (Thanks to @thelegendofmario)
• Made sure the body is always at least the height of the screen, to prevent background tiling
• Use x-cloak on elements that use x-show, to prevent a "flash" of content as Alpine.js initializes
• Added a system for the user to view how much space any local offline data is taking up, and give them the option to remove it
  • This is broken up into categories, the user can remove scouting reports, backed up scouting reports, and pit scouting data
  • The user is also warned if their browser is reporting the site has almost used all of it's capacity
• Removed django-browser-reload as it didn't seem to work correctly
• Created a user management system
  • user.js now handles user authentication
  • Additionally, a settings system has been added. Settings are configured by adding to the Settings model in the backend, then they can be access in the frontend using user.js
  • Using these new systems is documented here
• Made some improvements to the event selector, making it easier to use
  • Additionally, authenticated users are now able to favorite events in the event selector
  • These events appear in a separate tab, so they can be found faster
  • Additionally, a loading indicator has been added for while the event list is loading

Issues closed:

• #67 - Change the colors of true and false values in the charts in the advanced data view
• #94 - Use x-cloak on elements that use x-show
• #84 - Warn the user if their device may clear any local offline data
• #68 - Be able to favorite events to pint them to the top of the event list
• #28 - Add loading animation to event selector

v0.1.7-alpha

This release adds the ability for users to reset their password if it's forgotten, and adds a page to allow the user to change their profile information

In this release:

• Add the ability for the user to change their password on the authentication page if it was forgotten
  • The user is sent a verification code to reset their password
• Added django-browser-reload to automatically reload the page when changes are made
• When the developer settings are opened in the menu, the menu is now scrolled to the bottom to reveal all of the options
• Created a page to allow the user to edit their profile details
  • For now the user can change their display name and team number
  • Later this page will be used to handle user settings and other user specific options

Issues closed:

• #48 - Forgot password in authentication
• #86 - Scroll to the opened section when expanding sections in the menu
• #47 - Be able to edit user profiles

v0.1.6-alpha

This release adds several quality of life features and optimizations, and fixes some bugs

In this release:

• Auto save match scouting progress, so if the page crashes or the user accidentally reloads, progress isn't lost
• Fixed an issue where charts in the advanced data view wouldn't update when the filters do
• Optimized the advanced data page by only rendering data that the user has expanded to show. This greatly increases load times and snappiness
• Added a button to collapse all sections in the advanced data view
• Fixed getting the wake lock permission on the contribute page
• Fixed an issue where the authentication page couldn't be loaded
• Updated issue templates

Issues closed:

• #77 - Auto save match scouting progress
• #70 - Charts in the advanced data view don't update when the filters do
• #90 - Fix wakeLock on the contribute page
• #89 - Issues with loading the authentication page

v0.1.5-alpha

This is a small release that mostly makes changes to documentation on the development process, and adds a few new features

In this release:

• Fixed development installation instructions and added recommended workspace extensions (For VSCode)
• Moved the production installation docs into a separate file
• Hopefully fixed VS Code tasks to work on more OSes
• @GoldGaoler Adjusted some colors and animations on the menu buttons
• Re-implemented the ability to sort data in the advanced data view
  • Users can sort by average field values in ascending or descending order

Issues closed:

• #73 - Reimplement the ability to sort data in the advanced data view

Contributors in this release:

• @GoldGaoler