-
Notifications
You must be signed in to change notification settings - Fork 286
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
Update ESLint and enable more rules #572
Conversation
111:20 error 'Namespace' is not defined no-undef
|
||
const EmberDebug = EmberObject.extend({ | ||
|
||
application: null, | ||
started: false, | ||
|
||
// Using object shorthand syntax here is somehow having strange side effects. | ||
// eslint-disable-next-line object-shorthand | ||
Port: Port, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What were the side effects? My first guess is because the es6 module is being transpiled before Babel so Port
import is being transpiled to Port['default']
before Babel gets the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
huh, that might indeed explain things... I've got another PR waiting that ditches the es6module plugin and uses Babel for that like Ember CLI does too. Once that is merged we can remove the comment and use the shorthand syntax.
❤️ !!!! |
Looks good to me. Is this ready to merge? |
@teddyzeenny should be ready to merge from my side. Thanks for the quick review! |
Can you squash the ESlint rules into one commit? |
@teddyzeenny done |
/cc @teddyzeenny