We could save the version number inside indexedDB and display a snackbar, whenever the version number changes. The snackbar could contain a link to the github release-page, so that the user can easiliy see what the update brought.

We currently just show a simple component, which contains a hint that the users needs to select at least one stand alone expansion inside the settings.

We should additionally provide a "link" to the settings. (meaning some clickable text, which triggers the routing step)

https://reactjs.org/docs/hooks-faq.html

We currently always show which expansion a Nemesis/Mage/Card belongs to.
It would be cool to be able to provide a storage key to each expansion inside the settings.
If such a key has been provided by the user, we will show it instead or additionally of/to the expansion.

That way the user does not need to remember that they have stored Xaxos and Brama inside a sock under their kitchen table...

Meta tags and stuff...

Reverse the discard and deck order so that the last drawn card is at the top of the turn order table

A user on reddit pointed out, that some market setups are not legal - at least by the rulebook.
While I would say these are technical legal, because the come from the designer of the game himself, it might be useful to add a small indicator, that they are not? I am not sure actually.

Setup: In the Supply tab, after creating a market with any setup, the market setup template is changed by the user (via the drop-down menu).

Expected behavior: All current market cards are cleared and the new template is shown.
Actual behavior: The new template is shown, but the market from the (now deprecated) market template is still visible. This creates an inconsistent view.

Please clear the market cards after the setup is changed.

The app is starting to become rather complex. I think we should probably integrate redux soon, to make state handling a lot more explicit.

NOTES

• Keep CRA-Information
• Add CI-Badges
• add PUBLIC_URL env-var tipp for better local PWA testing
• Add contrib guidelines
• Add app description
• #95

• Reverse deck card orders
• highlight current drawn card
• write into indexdb

Simply put the string value into indexedDB^^

Change theme color to teal and sync with splash screen and app logo color

Why

• The markup generated by Material-UI is quite ugly
• Performance is underwhelming
• Extending styles is awkward
• API is not intuitive to use

Proposal

Lets switch out Mui-components with our own custom styles components.
This could be done step by step.
That way we could also lower our bundle size.

Multiple commits and Merge Requests possible, before we merge this. We should create some subtasks

• Turnordersetups:
  • alternate Wild setup with token
  • 1/3 2/4 (or was it 1/2 3/4?) cards
• Blitz Card (Buried Secrets)
• Malestromcard (Legacy)

• Add basic manifest
• Add service worker features to save user settings

Thought: Maybe we should persist the currently generated items as well, to prevent them from being deleted on a pull-down-refresh in chrome

Still feels sluggish probably largely due to the heavy use of Mui-Components. There might still be some room for improvement, though...

I am not sure how useful this feature actually is. But the idea ist interesting. For a bit more background, read this comment form BGG user Leigh Hathaway:

Firstly, they advise that based on their code some of the legacy cards are rated as either too weak (Ia, Id, II) or too strong (V, VI and VIII). 
Maybe there's a way you could inform users whether they have random selected a hard or easy supply deck based on the legacy cards included.
Secondly, Legacy introduced the Pulse mechanic which is powerful when combined with a couple of other Pulse objects but maybe too weak if a single Pulse item comes up.
Maybe users could choose a Pulse strong hand or no Pulse cards?

Because it is currently not possible to create custom setups, yet, many users want an inclusive version of market 1.

Write tests for turn order deck feature

TODOs

• Add supply selection to settings
• Add custom supply tab with checkboxlist
• Add addSupply-button
• Operations:
  • Add -> isNew: true, isDirty: true
    • Automatic ID creation
  • Edit -> isNew: false, isDiry: true
    • Name Input
    • addCard:
      • Type, operation, threshold/values, cost
  • Save
  • Cancel
  • Delete
• Manage edit in local component state and only commit changes to redux on save
• Show supply (some kind of Preview)
• save custom supplys to indexedDB
• fetch custom supplys and setup config
• Read from selection
• Fix bug that causes to evaluate supply order wrong (e.g. relic is first blueprint, but shown as last in supply)
• Styling