JsonAPI was proposed as there are plenty of implementations in JS, in Python and should reduce some bikeshedding

With the current state of #12 every record is being fetched and not cached. Should leverage Orbit's in-memory data store with the server fallback: https://orbitjs.com/v0.15/guide/getting-started.html#Communicating-with-a-server

The goal is to keep the database schema in sync with the business logic so down the line we're not trying to run old business logic against a version of the db we can no longer recreate. Migrations allow us to keep the db and what operations occurred on it in version control

Potential solution: Flask-Migrate

setup docker dev env w/ volumes

TODO:

• Get rid of the index.js files in pages and components
• Move purely utility components elsewhere
• Make storybook run-able independently
• Add notes to stories
• Rename story files? .story.js?
• Figure out how to generalize forms/
• Replace tailwind with styled components?

• api/login

  • Send username and password and should return a JWT if the credentials are valid, 401 if not

• api/logout

  • Logs out the current user for the supplied token

• sessions/current

  • Returns the current user for the supplied token

Do we need that directory or can we fix the permissions on it?

members/me doesn't work with the current in memory data store implementation using remote ids