SquireCore
SquireCore copied to clipboard
The backend library used by Squire Tournament Services
Updates the requirements on shuttle-runtime to permit the latest version. Most Recent Ignore Conditions Applied to This Pull Request | Dependency Name | Ignore Conditions | | --- | ---...
Updates the requirements on [cookie_store](https://github.com/pfernie/cookie_store) to permit the latest version. Changelog Sourced from cookie_store's changelog. [0.21.0] - 2024-02-08 Miscellaneous Tasks Update CONTRIBUTORS.md Ci Add missing v0.20.1 CHANGELOG entries Rm --topo-order...
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 3 to 4. Release notes Sourced from codecov/codecov-action's releases. v4.0.0 v4 of the Codecov Action uses the CLI as the underlying upload. The CLI has helped to...
It compiles at least. Seems like the core stuff were handlers for stores that should be permanent. The stuff in clients were created with different ids and such so they...
Updates the requirements on [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite) to permit the latest version. Changelog Sourced from tokio-tungstenite's changelog. 0.21.0 Update TLS dependencies. Update tungstenite to 0.21.0. 0.20.1 Fix RUSTSEC-2023-0053. Fix transitive CVE-2023-43669 from...
## Description: The current tournament UI is best described as functional. It is not pretty or very intuitive. A fresh pair of eyes should look at the tournament UI to...
## Unmet Need: SquireWeb needs pages for users to login and register. This should redirect them to the tournament creation page.
## Unmet Need: While functional and generally applicable, our current actor model is mostly designed for actors that are: - Meant to live forever - Always able to receive and...
## Unmet Need: The pairings and standings are both limited in their sorting options and are not the most helpful to players and tournament staff. For pairings, we only give...