Skip to content
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

Support component.jsonc config files #20

Open
ocombe opened this issue Aug 17, 2021 · 0 comments
Open

Support component.jsonc config files #20

ocombe opened this issue Aug 17, 2021 · 0 comments
Labels
feature New feature or request
Projects

Comments

@ocombe
Copy link
Member

ocombe commented Aug 17, 2021

For options that are specific to one component, we shouldn't require a new custom env (custom env make sense when they are used for multiple components). Custom env are linked to a specific workspace and are not automatically imported when you import a specific component.
This would for example allow users to set specific global scripts and styles for all of the compositions.

The options should be similar to what we can find in angular.json files.

@ocombe ocombe added this to This week in Roadmap Aug 17, 2021
@ocombe ocombe added the feature New feature or request label Aug 17, 2021
@ocombe ocombe moved this from This week to This month in Roadmap Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
Roadmap
This month
Development

No branches or pull requests

1 participant