-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(typescript-estree): clarify default file extensions #963
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.
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
chore(typescript-estree): clarify default file extensions #963
Conversation
Thanks for the PR, @dimitropoulos! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs are great, but code would be even better! :)
Please could we add actual validation and feedback to the code that handles this? e.g. if a user gives values which are already handled by default, we tell them. If they give values which don't start with a .
we tell them etc
Thanks again for contributing! This kind of feedback that comes from real world experience is invaluable
@JamesHenry ok. I added something, but I have to say I'm not up to speed on this project so I:
Hopefully that's at least a start? Sorry I can't do more right now (I need to focus on a separate problem I'm experiencing with the parser that's holding up my team). |
you will have to modify the unit tests in you can add tests for your new code in there as well. |
@bradzacher I'm sorry, I won't be able to do more with this out of lack of time. If you would like me to remove the code and just update the documentation please let me know and I will happy do so. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks for picking this up @armano2
we should add test cases for this |
I was doing a few things wrong that encouraged me, whilst debugging an issue with the parser, to make these changes.
I was using
"extraFileExtensions": ["tsx"]
in my code. For one thing,tsx
is already scanned. For another thing, the format of this (which mirrorspath.extname
) is such that the.
is required to work properly.Once I read the source code and better understood how it really works, I decided that a simple mention of the defaults, as well as an explicit example, could have prevented me from going astray.