We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
design files
I think it could be useful in terms of developer experience to write the style of the components close to the component it self, for example:
developer experience
-- src -- -- components -- -- -- MyComponent -- -- -- -- MyComponent.tsx -- -- -- -- MyComponent.morfeo.ts -- -- -- -- index.ts
The content of MyComponent.morfeo.ts can be something like:
MyComponent.morfeo.ts
export default { tag: 'button', style: { bg: "primary", borderRadius: "m", px: "l", // ... }, variants: { // ... }, }
Then, by running something like:
morfeo build-theme
The CLI will find all the {componentName}.morfeo.ts files and merge in the main theme:
{componentName}.morfeo.ts
// theme.ts export default { colors: {....}, spacings: {....}, // ... components: { [componentName]: { // ... content from {componentName}.morfeo.ts } }, }
The text was updated successfully, but these errors were encountered:
feat: compose command wip #40
d83a154
2ce5b9a
018105e
ae13a59
0b186f4
199a1c6
mauroerta
Successfully merging a pull request may close this issue.
Merge
design files
in the main themeI think it could be useful in terms of
developer experience
to write the style of the components close to the component it self, for example:-- src
-- -- components
-- -- -- MyComponent
-- -- -- -- MyComponent.tsx
-- -- -- -- MyComponent.morfeo.ts
-- -- -- -- index.ts
The content of
MyComponent.morfeo.ts
can be something like:Then, by running something like:
The CLI will find all the
{componentName}.morfeo.ts
files and merge in the main theme:The text was updated successfully, but these errors were encountered: