Fix issue with naming-convention in bare mode and nested Input types

[jamessharp]

Description

Using the naming-convention transform in "bare" mode, it doesn't correctly transform nested field argument Input types. See #4895 for details.

The code for this transform was only operating at the root level of any Inputs when considering field arguments. This fix adapts the code to fully iterate through any Inputs, including nested ones.

Fixes #4895

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Modified the bareNamingConvention spec to include this scenario

Checklist:

• I have followed the CONTRIBUTING doc and the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests and linter rules pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[changeset-bot]

🦋 Changeset detected

Latest commit: 6e52c8a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@graphql-mesh/transform-naming-convention	Patch
grpc-example	Patch
grpc-reflection-example	Patch
json-schema-example	Patch

Not sure what this means? Click here to learn what changesets are.

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

[ardatan]

Could you add a changeset with yarn changeset? Thanks :)

[jamessharp]

Done

[santino]

Hi @jamessharp ,
thank you so much for your contribution to the bare implementation of this transform.

Can I ask you to run yarn prettier just to align the formatting to the project standards and make it easier to follow the changes?

I had a look at your changes and I will be doing some testing soon; so it won't hopefully be long since we are happy to merge this.

[jamessharp]

Ah - I think your prettier config may have changed - I've just run yarn prettier and now have 267 files changed, which would explain the changes in this PR (I have "run prettier on save" enabled in vscode)

I'm more than happy to commit the extra , or manually undo the prettier changes in this PR, as you see fit!

[ardatan]

I think we can take of prettier later. So if it is good for you other than prettier @santino , we can merge it.

[jamessharp]

Hi @ardatan / @santino - any update on this? I've just rebased it onto the latest master.

[ardatan]

I don't have an access to your branch so creating a new PR.
Thanks for the fix!