-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Component refactor and toolkit #545
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't you think it should be placed in src/components/custom
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't think it was urgent but yes, absolutely. I'll create a Jira ticket so that we don't forget.
This PR introduces the concept of "toolkit", namely:
core
(collection of all the component templates we now until now, including Section, Page, etc)workflows
(new collection for Workflows)It also updates the mode switcher so you can choose 4 modes:
A switch in mode determines which toolkit is shown; only the Workflows mode shows the
workflows
toolkit.There's also been a refactor in the
core_components
folder to allow for a neater hierarchy that can accommodate the two toolkits,core
andworkflows
. Paths have been updated to use the "@/" syntax, since the relative syntax was getting out of hand i.e.../../../injectionKeys
etc.