Skip to content

Version 12: March 13, 2019 07:35:05 AM

Choose a tag to compare

@mxxk mxxk released this 13 Mar 07:35
34be5a9
Make data model more flexible (#25)

So far, we have had a very well-defined and rigid data schema. Every meeting has a General Evaluator. Every meeting has up to two speakers. And so on... As the app moves forward, it is beneficial to relax some of these constraints and allow for flexible meeting roles. This PR is the first step in that direction.

Because current instances of the app are using the previous data model, this PR only makes new instances of the app use the new data model, and leaves the previous data model and corresponding React components which access it in place... for now. :wink:

After this PR is in place, the next steps are to:

1. Write a migration function to move data from the old model to the new.
2. Completely remove the old data model and React components.

Features
========

- Speech project selection and cancellation is _live_! When a document is opened in multiple places, these changes will get synced between them. :smile:
- New data model makes it possible to have custom roles in the future.
- React components are organized between multiple files.
- CSS modules isolate styles with auto-generates classnames.