@rename directive not affect @rules validation

[NatanielMarmucki]

I have a question regarding the behavior of the @rename and @rules directives in Lighthouse, especially when using Laravel validation.

We use Laravel validation, which expects keys in snake_case (e.g. billing_id). However, even when I apply the @rename(attribute: "billing_id") directive to the billingId field in my GraphQL input, the validation performed by the @rules directive (for example, exists:billings,id) still refers to the original GraphQL argument name, billingId, not the renamed billing_id.

As a result, I have to define both billingId and billing_id in my translation files, which causes confusion and breaks Laravel conventions.

Is there a reason why the @rename directive does not affect the keys used during validation by @rules?
Is it possible to make validation work with the renamed keys, or are there any plans to change this behavior in Lighthouse?

[spawnia]

Is there a reason why the @rename directive does not affect the keys used during validation by @rules?

It just was not implemented that way, doing anything at all with @rename requires more effort and consideration.

I can see where you are going with this and am open to reviewing a pull request that explores this behaviour change but am not looking into it myself.