Previously: (Pilot having views based on React, without needing to do that entire declarative authorization refactor.)
[ ] The process of doing webpacker and npm and yarn etc. is well documented for devs
[ ] There are examples of test cases for the React code, and those are run when CI is run.
[ ] There are examples of test cases for the backend API calls.
This enables us to divide up future dev efforts between front-end React stories, and backend Rails development.
Then, future implementation can follow this model.
Already done in another issue:
[x] The React app is being served out of Rails... (as demonstrated in the Spike from Summer 2019). You embed the React app in Rails.
[x] There is an example in the code base of a page that uses React to fetch and display data
[x] That example has a backend RESTFul JSON API that does appopriate authentication of the
user to whatever data they are accessing (the react app can phone home with authorization
and authentication.)
Previously: (Pilot having views based on React, without needing to do that entire declarative authorization refactor.)
webpacker
andnpm
andyarn
etc. is well documented for devsThis enables us to divide up future dev efforts between front-end React stories, and backend Rails development.
Then, future implementation can follow this model.
Already done in another issue: