mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-13 01:54:52 +08:00
Tim van der Lippe
2c89197d0d
R=jacktfranklin@chromium.org No-Presubmit: True Bug: none Change-Id: I52dc24b12e350787085c5e3d131cface7ea87142 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3060705 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Paul Lewis <aerotwist@chromium.org>
1.2 KiB
1.2 KiB
import/no-named-as-default
Reports use of an exported name as the locally imported name of a default export.
Rationale: using an exported name as the name of the default export is likely...
- misleading: others familiar with
foo.jsprobably expect the name to befoo - a mistake: only needed to import
barand forgot the brackets (the case that is prompting this)
Rule Details
Given:
// foo.js
export default 'foo';
export const bar = 'baz';
...this would be valid:
import foo from './foo.js';
...and this would be reported:
// message: Using exported name 'bar' as identifier for default export.
import bar from './foo.js';
For post-ES2015 export extensions, this also prevents exporting the default from a referenced module as a name within that module, for the same reasons:
// valid:
export foo from './foo.js';
// message: Using exported name 'bar' as identifier for default export.
export bar from './foo.js';
Further Reading
- ECMAScript Proposal: export ns from
- ECMAScript Proposal: export default from