Need to have an api to expose collected data.

Prob at least needs:

• spec based mocks
• Hero data
• Item data
• Match data (just forward gathered data from valve api)
  • Paging
• Most common heroes
• Most successful heroes
• Common combos?
• Worst at playing against
• Best at playing against

Frontend is sort of functional now, but still rough/missing a lot

TODO

• gql mocks
• Match views
  • needs items/resources in backend
• Player views
  • needs player info exposed as root query
    • Display name
    • Profile pic link
• Analysis views
  • Core
  • Expand
  • key errors
    • Probably fixed with real data (or at least easier to fix)
  • Some sort of per query modal display thing?
    • Not useful until more queries added
• Router support

https://github.com/matthewReff/Locket-Match-Queries/blob/4dce80b81f8427c20a5eeeb68a81cce55ccd086f/src/locket_match_queries/core.clj#L34

Currently everything is half switched over to yarn workspaces.

Here's a handful of related small issues:

• Generic

  • make consistent format/lint/other scripts

• Frontend

  • Add ci tasks (probably just a build)

• Backend

  • ci is still using clojure directly. Use yarn instead for consistency

• DB

  • build doesn't do anything. Should prob build it's tag before backend builds.
  • run should run a dev image. Maybe add a sane config to backend too?

Steam api allows pulling contiguous matches from a user starting at a specific id. In order to know where to start pulling, you need the last match that was pulled for that user, not just the last cached match where that user played.

Neutral items missing in additional_units, too many backpack slots, none of them are foreign keys. While fixing can factor out to a new inventory table to avoid duplication.