mathematicalthinking/vmt

Refactor Redux

Closed this issue · 0 comments

It seems we've just haphazardly created actions and action-creators as we need them without much though given to design...A lot of functionality is unnecessarily duplicated because we do similar things for rooms and courses...and worse, a lot of the duplicated functionality is just ever so slightly different. For example, removing removUserRoom"S" vs removeUserCourse.

Step 1 would be to

  • redesign actions and reducers, perhaps base it off of the backend controllers so that we can share a lot of the common actions for different resources in a shared directory.