This repository has been archived by the owner on Feb 22, 2023. It is now read-only.
Add eslint-plugin-import to enforce import order and extension consistency #855
Labels
🤖 aspect: dx
Concerns developers' experience with the codebase
🧰 goal: internal improvement
Improvement that benefits maintainers, not users
good first issue
New-contributor friendly
help wanted
Open to participation from the community
🟩 priority: low
Low priority and doesn't need to be rushed
🚦 status: awaiting triage
Has not been triaged & therefore, not ready for work
Problem
There is no enforced consistency in how we import modules in JavaScript. Sometimes we use extensions for
.js
files and other times not.In https://github.com/WordPress/openverse-frontend/discussions/465 we decided that it'd be good to enforce consistency here using eslint.
eslint-plugin-import
has tons of helpful rules for this.Description
Add
esling-plugin-import
to the eslint configuration.Implementation
The text was updated successfully, but these errors were encountered: