feat: add filename case support #388
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This allows users to control the naming convention of generated resolver files, supporting common filename formats, while preserving original default functionality. Details: - Add change-case-all dependency to typescript-resolver-files package - Add fileOutputCasing config option with 'pascal-case' (default) and other casing support - Update preset config validation to include fileOutputCasing option - Add transformResolverFileName utility to convert resolver names to appropriate filename casing - Integrate filename transformation throughout the resolver generation pipeline - Add unit test coverage for filename transformation functionality - Add e2e test suite - Update documentation in README.md
jruhland
force-pushed
the
feat/add-filename-case-support
branch
from
407291a to
65cc142
Compare
jruhland
changed the title
|
Thank you! I'll take a look soon 👀 |
|
No hurry/pressure, but let me know if theres anything I can do to help out here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not 100% sure of the standards on the repository, so just going to throw this up as this has been an area of friction for our team using the plugin.
We want to allows users to control the naming convention of generated resolver files,
supporting common filename formats, while preserving original default functionality. Separate of the contents inside the file.
Details: