dinghy http proxy (See Readme of cs-node-app-template, Development environment chapter)
Steps
Check out master branch of cloudstorm
Modify the sample.js file to use the commented out MainCtrl (don't forget to comment out the other one)
Check out cs-model branch of cs-node-app-template and follow the readme's instructions to get it up & running (without the frontend app) - use the cloudstorm sample app to modify the resources
Create a few teams and a few coaches, assign the coaches to teams, so there are data in your local db
create a new Coach and during the creation create a new Team
The error should be visible: all coaches will have the newly created Team on the index. A refresh solves the problem, so the data on the backend is okay, but the FE datastore is messed up.
Pictures
State before adding a new coach:
Adding a new coach with a newly created Team:
State right after adding:
State after a browser refresh:
This is one example of a bug, where the FE datastore is not in sync with the backend data, but there are more instances where the same problem causes similar problems. Please test the frontend app thoroughly with the provided backend where different associations are available and document all the issues you find (So create issues for the different variations of the issue after solving this one.)
A non-complete list of things to test:
Add/delete/edit items with associations, create new items through the wizard
Order/Filter - should be kept after adding/deleting/editing items
Delete associated items, check the associatee
One more thing to note: There are many unnecessary calls to the backend (you can trace all backend calls in the log of cs-node-app-template), please also create issues when more calls are made to the backend that necessary.
How to reproduce:
Prerequisites:
Steps
Pictures
State before adding a new coach:
Adding a new coach with a newly created Team:
State right after adding:
State after a browser refresh:
This is one example of a bug, where the FE datastore is not in sync with the backend data, but there are more instances where the same problem causes similar problems. Please test the frontend app thoroughly with the provided backend where different associations are available and document all the issues you find (So create issues for the different variations of the issue after solving this one.) A non-complete list of things to test:
One more thing to note: There are many unnecessary calls to the backend (you can trace all backend calls in the log of cs-node-app-template), please also create issues when more calls are made to the backend that necessary.