codeforboston / codeforboston/cliff-effects

Use default exports by default

Open
#902 6 comments 0 reactions 0 assignees View on GitHub
discussion needed infrastructure tech-debt
Dominant language
JavaScript
Stars
30
Forks
62
PR merge metrics
No merged PRs in 30d

Description

For many components, we are currently using named exports instead of default exports (e.g. `import { MyButton } from './MyButton`; rather than `import MyButton from './MyButton';`.) I feel like we should be using default exports for components, with named exports only if it needs to export additional symbols.

This is a somewhat stylistic question; thoughts? Anyone feel strongly otherwise?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.