Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Naming strategy doesn't applied to query builder return value #39

Open
HYOSITIVE opened this issue Feb 15, 2023 · 1 comment
Open

Naming strategy doesn't applied to query builder return value #39

HYOSITIVE opened this issue Feb 15, 2023 · 1 comment

Comments

@HYOSITIVE
Copy link

HYOSITIVE commented Feb 15, 2023

I've recently found out that naming strategy doesn't applied perfectly when I use it with query builder.
More precisely, it works when I write queries, but it doesn't work with the returned value by the query builder.
I'll attach my example below.

image

image

I think if I don't specify aliases with 'as', keys might be ambiguous if I join extra tables, so it might return snake case names.
But I hope camel cases are returned when I specify their aliases.
In my example, user_manner_point to userMannerPoint, or userispro to userIsPro.

Did I miss something or does this package not support this currently?

@HYOSITIVE HYOSITIVE changed the title Naming strategies doesn't applied to query builder return value Naming strategy doesn't applied to query builder return value Feb 15, 2023
@JayPe69
Copy link

JayPe69 commented Oct 12, 2023

Hello,

when using getRaw ... it does not apply.
but when using get... it applies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants