Is there a way to prevent relationships being converted to camel case?

[Ekion-1]

Is there a way to prevent this package from converting relationship names to camelCase? All of the relationships in my application are snake_case.

[AlexVanderbist]

Currently there isn't... I wrongly assumed camel casing relationships was required or best practice for Laravel.

I'm open for suggestions tho (maybe looking for the matching relationship regardless of case?) - feel free opening a new issue if you want to discuss implementing this :)

[pionl]

Hi there, I've got the same problem. My point of view is, that it should not convert values from includes array and leave it as it is (so, if you have myRelation, you should use includes(['myRelation')).

Of course it would break current applications using the query builder - I've would suggest to use a config that would turn this behavior.

-- Edit

I've cloned the repo and noticed that maser version does not use camel case, is that correct? It appears I need to update the logic to use 2+ (I'm on 1.16.1)

[suth]

I've also run into this issue. Seeing as how the conversion was built around an incorrect I see no reason to leave that mistake in place. I tried extending the AllowedInclude class to omit the camel casing, but it seemed like there was somewhere else I missed that was applying it as well.