Comments (3)
Hmm, okay. This makes sense 👍
But, currently lots of us do smth like:
import Ember from 'ember';
const { $, RSVP } = Ember;
So we already use $
and RSVP
directly which complicates this rule a bit.
I'm thinking about actual implementation of this rule. And it looks like apart from looking for Ember.$
and Ember.RSVP
we need to check for the existence of import $ from 'jquery';
and import RSVP from 'rsvp'
and then if they don't exist but $
or RSVP
are being used - we can assume they're from Ember
namespace so we can point that they are supposed to be imported directly, not destructed from Ember.
What do you think @Turbo87 about naming this rule require-direct-imports
or something similar? We can mention in documentation which modules are now supported. In the future I guess there will be more of them, so making it more generic now might have a sense.
from eslint-plugin-ember.
FWIW https://github.com/ember-cli/ember-rfc176-data has more information on the suggested new import paths
from eslint-plugin-ember.
I'm wondering if we should add this rule or create one that will report all global imports regarding this list: https://github.com/ember-cli/ember-rfc176-data/blob/master/globals.json as part of #86
from eslint-plugin-ember.
Related Issues (20)
- New rule to lint against referencing `let` variables in `<template>` HOT 1
- New Rule: no-render-modifiers
- New lint: potential bug with assigning a value to a tracked property
- new lint: do not use 'this' in tests in gjs/gts files
- New lint: prevent usage of `Input` and `Textarea` (the ember default components) HOT 3
- [email protected] detects single-line components as zero-line components HOT 3
- Parsing error for template tags within classes on v11.11.0 HOT 6
- Drop Recommended Rules for Deprecated Ember 3.x Features HOT 2
- Replace ember-template-imports with content-tag HOT 2
- New rule proposal: require-components-imports-pascal-case HOT 2
- config files in readme should not encourage top level config. overrides only.
- ESLint couldn't find the config "plugin:ember/gts-recommended" to extend from HOT 4
- false positives for `no-unused-vars` in `gjs` files, when using `<Component as |something|>` HOT 3
- gjs/gts Incorrect token mapping after handlebars HOT 1
- Support "Type aware" linting for gts files HOT 13
- "service" import not treated the same as "inject as service" HOT 1
- no-unused-expressions HOT 4
- Plan v13 Release HOT 4
- new "flat" configs contain invalid parser key HOT 19
- `@typescript-eslint` breaks after update to `eslint-plugin-ember` v12 HOT 19
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eslint-plugin-ember.