New Octane Rule: `no-classic-components`
See original GitHub issuePulled from https://github.com/ember-cli/eslint-plugin-ember/issues/533 which proposes a new set of rules for Octane related best practices
Disallow usage of the @ember/component
base class. Use @glimmer/component
instead.
// ### Good
import Component from '@glimmer/component'
// ### Bad
import Component from '@ember/component'
If anyone would like to implement this please comment that you’ll take it and work away.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Introduce an `octane` configuration · Issue #533 · ember-cli ...
Recently ember-cli-template introduced an octane configuration which guides users to use new Octane patterns over classic component patterns.
Read more >How to automatically keep track of the octane update process ...
i would like to keep track of the progress automatically maybe via a github action or script to identify files which have been...
Read more >eslint-plugin-ember | Yarn - Package Manager
NPM version NPM downloads CI. An ESLint plugin that provides a set of rules for Ember applications based on commonly known good practices....
Read more >The Octet Rule - Chemistry LibreTexts
The octet rule refers to the tendency of atoms to prefer to have eight electrons in the valence shell. When atoms have fewer...
Read more >eslint-plugin-ember - npm
Note that new rules should not immediately be added to the recommended configuration, as we only consider such breaking changes during major ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m taking this one 😃
@bmish could you assign this issue to @mikoscz please?