-
Notifications
You must be signed in to change notification settings - Fork 115
Moving to a more stable way of compiling the styles #333
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
57ab46e
to
8166fb9
Compare
rather then generating a single `pod-names.js` file with all of the namespaced styles, moving to a mechanism where each style file set (style files that are shared the same namespace at the same depth) gets it's own `style-info.js` file that has the namespacing for that component. For components with a `component.js` file, using a babel plugin to import the `style-info.js` and add the styleNamespace as a class property, as well as adding it to the classNameBindings. For routing styles, using a lookup pattern where we are looking up the given namespace through the owner lookup. For components without a component.js, creating a base one that defines the import and sets the class with the layout. For template-only-glimmer-components, wrapping the contents of the template in a `let` block that defines the `styleNamespace`. * moving environment.js 'ember-component-css' config values to emberCliStyles values that are set in the ember-cli-build.js file. * Also deprecating the `pod-styles` name for the imported style file in favor of an `ember-styles` named file. * Also migrating things to their latest versions as well and moving things to proper classes. * Also using preprocessor registries rather then the `treeFor` hooks. * Also migrated the tests to use the latest modules and hooks. Setup some base acceptance tests that the different style types share.
in something like `import { foo as bar } from 'fee';` `foo` is the imported part, while `bar` is the local. we just want the local this enables one to import other `styleNamespaces` and use them in the component.
… building of routes, it should just recive an array
… a route for a cleaner and more predictable api
…e-manifest and broccoli-tree-walker
…needed, and pollished up some names
… when you remove, and I couldn't figure out how to get it back in a good state
…o latest versions
…amespace' in templates
…helper. This can be used anywhere, but is needed for template only components
ok. an "alpha" tag has been published with the version of 1.0.0-alpha.2 https://www.npmjs.com/package/ember-component-css/v/1.0.0-alpha.2 WIll create a new issue with the remaining work to get to a stable 1.0 version soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Breaking changes in this approach:
styleNamespace
in addon components needs to be explicitly added al lapod-styles
has been replaced withember-styles
podNames
that can be imported fromember-component-css/pod-names