Resolves #4953
Impact: breaking
Type: feature

Issue

Move the product administration tools (Product grid and detail page) into the Operator 2.0 experience.

Solution

• Reuse a mush code as possible while also updating the presentational component to fit into the new operator experience.
• Avoiding building anything data related. This means no GraphQL at this time, and minor modifications to the meteor trackers, composers and data fetching.
• This is a phase 1, and as such not everything will be perfected, and many of the bugs/hiccups that were prevelant in operator 1.0 product editing my or may not have been addressed.

Breaking changes (Super-duper-major)

Reaction is no-longer a customer facing app, it's an administration tool and offers a GraphQL api.

All customer facing views are the responsibility of a separate storefront app that makes use of the GaphQL api. See our example storefront as an example of how to achieve this.

Testing

Login

1. Ensure you can sign-in as an admin and that you're redirected to "/operator"
2. Ensure that if you sign-in as a non-admin, that you see the reaction logo, and a signout button
3. Ensure that if you sign in from the starter-kit, you are correctly redirected back to the starter-kit on successful sgin-in

Products

1. Load a bunch of products into the app
2. If you used sample-data ensure that after signin you go to http://localhost:3000/operator/localization and reload translations with the refresh button
3. Then go to http://localhost:3000/operator/products, or use the navigation bar item "Products"
4. Be amazed
5. Then, add, edit, publish products etc, products, variants, options and ensure changes are made as expected.