-
Notifications
You must be signed in to change notification settings - Fork 62
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
Custom naming strategy #975
Comments
Why not name your schema in camel case? that's what I do. |
It feels a bit inconsistent, because both the SDL and EdgeQL use snake case for everything. |
IMO that's the lesser evil, than trying to have naming translation for a specific client. |
I agree that a naming translation is bad, but it would be nice if we can do like Drizzle where you can "alias" the property name: { myAge: integer('my_age') } The SDL could support something like:
That way I can follow the naming conventions of EdgeQL and match the naming conventions of TypeScript. |
The whole JS ecosystem has the camel case convention for property names.
It would be nice if this JS client supports the same naming strategy feature from the DotNet client https://docs.edgedb.com/libraries/dotnet/customtypes#using-a-naming-strategy, so the property names in query results could be camel case enforced.
The text was updated successfully, but these errors were encountered: