reactioncommerce / admin-core Goto Github PK

Add notistack package and snackbar provider to the App component. This provides support for various UI's that display toast messages throughout the application.

The admin-core repo with be the first home for the core UI elements like layouts, sidebar navigation elements, toolbars used in the base UI in the previous Reaction Admin.

What will be moved...

• Most of the UI elements from /imports/client/ui will be moved to this repo as it's the first destination.`
• Components that don't have a counterpart in Catalyst. We can reassess later what elements of them belong in Catalyst as some of them depend on data from GQL directly.
• Blocks API

What will not be moved...

• Anything Meteor specific will not be moved. These things will be reworked as necessary.
• Any components that have a counterpart in Catalyst
• registerOperatorRoute will not be moved, but re-built in admin-core to meet the needs of React components only.

We need to be able to configure the now hard-coded variables in create-hydra-client.js to be able to support different app configurations.

• The default would be using a .env file with docker or .dotenv
• An alternative would be to see if we can do it with a config.js

Whichever makes the most sense this type of helper.

Add circleci config and prepare the package for semantic releases

Add Jest testing to this project. See project https://github.com/reactioncommerce/catalyst for an example

Add dev and production docker-compose configurations to this project.

• Move all of the Base UI components to Catalyst
• Allow base app component to be passed in

Issue

• test-utils were not transpiled on package build
• jest config cannot be used in downstream projects
• async/await isn't supported
• fetch isn't globally polyfilled

Add our standard suite of eslint configurations

Create an admin repo that will use admin-core as a library. The "admin" repo will effectively become the new "Reaction Admin".