Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enforce file extensions #303

Open
Pytal opened this issue Feb 15, 2022 · 2 comments
Open

Enforce file extensions #303

Pytal opened this issue Feb 15, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@Pytal
Copy link
Contributor

Pytal commented Feb 15, 2022 •
edited

The JavaScript ecosystem is increasingly standardizing towards requiring explicit file extensions on import paths e.g. Node.js 14 docs, we should think about adding the enforceExtension option to a new major release as long as it doesn't break anything as is common with making the necessary quantity of line changes in a dependent codebase
@Pytal Pytal added the enhancement New feature or request label Feb 15, 2022
@Pytal Pytal mentioned this issue Feb 15, 2022
Closed
@ShGKme
Copy link
Contributor

ShGKme commented Apr 18, 2023

Btw, extensions are required by @nextcloud/eslint-config with a warn.

https://github.com/nextcloud/eslint-config/blob/bd013875d845688d23e41e5a2ad66fcc2f36f05c/index.js#L117-L118

@Pytal
Copy link
Contributor Author

Pytal commented Apr 18, 2023

Btw, extensions are required by @nextcloud/eslint-config with a warn.

nextcloud/eslint-config@bd01387/index.js#L117-L118

Turns out I did that nextcloud-libraries/eslint-config#292 :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Pytal @ShGKme