-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Allow specification for file extension to be used in import statement paths for files created by code generation #4645
Comments
Seems reasonable. File a PR? |
I dont' have the code written for this request. I'm inquiring to see if you guys could add this feature. |
@TheMartianMaker Yeah, I'm saying it's a reasonable request, but it's probably not something we're going to have time to implement ourselves any time soon. Best bet to add it soon is if you can file a PR to make the changes, otherwise it'll probably be a while. |
@markerikson the PR has been filed :) |
@markerikson any updates? |
@TheMartianMaker no, the codegen has been low priority - all my own time atm is focused on pushing the infinite query feature forward. |
@markerikson i understand, and have already written the code to adapt the code gen. Are you waiting to complete infinite query before merging other PRs? |
Loosely, yeah. I've learned over the years that while I can absorb a lot of info, when it comes to large projects I can only deal with one at a time. That's especially true with something like a large RTK feature, where I only find time to work on it intermittently. It's also a matter of prioritization. |
Feature Request:
Use Case:
For ESM projects, it is often required to include file extensions in import statements. Currently, developers have to manually update the import statements in the generated files to include the necessary file extensions. This feature would automate that process and ensure consistency across the codebase, which is crucial for maintaining proper module resolution in ESM environments.
The text was updated successfully, but these errors were encountered: