-
Notifications
You must be signed in to change notification settings - Fork 87
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
Make target file extension configurable #6
Comments
By the looks of it, this change would affect only a few lines of code: ./src/utilities/readDirectory.js:36: return !_.includes(files, fileName + '.js');
./src/utilities/readDirectory.js:67: if (!isDirectory && !_.endsWith(fileName, '.js')) { As long as this feature is implemented sticking to principles of functional programming (without use or global state variables and tested), I don't have any objections against a PR. |
I figured I would just replace with
|
No, that could have unwanted side-effects, e.g. someone could have |
What's the status of this? @gajus ? Would be great to just do |
Not a priority for me. Will happily accept a PR. |
It is also useful for typescript but it doesn't generate index.TS... |
Would accept a PR. |
already implemented |
I use
.jsx
in my project (for ReactJS) so this currently will not work on my components folder.I could submit a pull request but wondered if you want to support user-configured extensions.
The text was updated successfully, but these errors were encountered: