jghibiki / bat-stats-api Goto Github PK

Create the data models to support list and deck editing.

KM's new filtering in list building is great, but it also needs to exist in the browsing section.

When viewing models within a rank, I think they should be filtered by rep cost. KM's app doesn't do this and it's infuriating! Within each rep cost, models should just be filtered alphabetically. So all models that cost 30 rep in a rank should just be filtered alphabetically, to make it simple.

In the same vein, I also feel like when you're browsing a crew, there should be a toggle to see all unaffiliated models that work for that crew. It should start in the Off position. This is very low on the list though.

Research and determine a good hosting provider.
Requirements:

• docker based python app
• postgres db

The API Scraper is partially implemented. Finish scraping the following entities, and the corresponding database models for those models.

• equipment
• traits
• upgrades
• weapons
• rule_documents

Reference List_Editor_Wireframes.drawio for the compact and full layouts.

Should also support custom nested controls, i.e. we may want a "+" button on one view and a "x" button on another.
Additionally, we should be able to pass in an equipment list to show additional equipment info under the traits section of the card.

Implement a basic authentication and authorization model for the app.

Crews should be shareable via links. If possible, the classic share button could be used to allow you to either copy the link or share it directly into another app.

The Azure builder did this very well imo, although the share button should be available in the list overview of crews and within the crew when viewing it.

Implement a basic api for creating, updating, and fetching lists and decks.

API should be accessible for authorized users only.

Reference List_Editor_Wireframes.drawio for the card/deck viewer component design.

Component should support customizable actions for each card, .e.g on some view's we may need to add / remove cards, on other views we would not want any nested controls.

Additionally, we should be able to pass in an equipment list to show additional equipment info under the traits section of the card.