feat: add filename case support

[jruhland]

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:

• 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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0b940c8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[eddeee888]

Thank you! I'll take a look soon 👀

[jruhland]

No hurry/pressure, but let me know if theres anything I can do to help out here.

[eddeee888]

Hi @jruhland,

I'm trying to think whether allowing filename case changes would open possibilities of naming clashes (the thought came from some of the unit tests - thank you!)

For example, if the option is snake case, would these two types have a file name clash in our file system?

type UserName
type user_name

Granted, it's unlikely codebases would allow a mix of conventions like this (but we never know 😅).
However, the current approach of using the exact type name as file name definitely avoids this potential issue.

[jruhland]

Hi @jruhland,

I'm trying to think whether allowing filename case changes would open possibilities of naming clashes (the thought came from some of the unit tests - thank you!)

For example, if the option is snake case, would these two types have a file name clash in our file system?

type UserName
type user_name

Granted, it's unlikely codebases would allow a mix of conventions like this (but we never know 😅). However, the current approach of using the exact type name as file name definitely avoids this potential issue.

Wow sorry missed this comment, and yeah good call out. Let me verify that, but yeah I think it would cause a collision (ive never seen snake case in graphql, but yeah im sure theres some funky codebase out there). WDYT about erroring out due to collision (only if this flag is enabled)?