df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Resolved conflicts by taking GitHub versions for: - .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml Kept deploy.sh updated to: - Pull from GitHub (primary source) - Push to Gitea (push-mirror) - Build from site/ directory (GitHub structure) Co-Authored-By: Paperclip <noreply@paperclip.ing>
705 B
705 B
import/no-named-default
Reports use of a default export as a locally named import.
Rationale: the syntax exists to import default exports expressively, let's use it.
Note that type imports, as used by Flow, are always ignored.
Rule Details
Given:
// foo.js
export default 'foo';
export const bar = 'baz';
...these would be valid:
import foo from './foo.js';
import foo, { bar } from './foo.js';
...and these would be reported:
// message: Using exported name 'bar' as identifier for default export.
import { default as foo } from './foo.js';
import { default as foo, bar } from './foo.js';