-
Notifications
You must be signed in to change notification settings - Fork 298
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
Incorrect casing for “ID” #1549
Comments
I attempted to use something like
to no avail to fix the situation. |
What I have not tried: |
Yeah, that assumption is baked into a lot of the TH code. I don't anticipate changing that to be easy or particularly flexible. |
Is there a combinator route to go, or is Template Haskell the only/preferred way? |
While you can define the |
All implicit generated IDs such as the ID for
Foo
is generated asFooId
. While much of the documentation uses “ID”, the code representation is incorrect casing where “ID” is the standard abbreviation form for identifiers (IDs), not “Id”. Changing this would align other correctly-cased variables in the project likeDB
(along with uses ofIO
,UUID
, &FromJSON
from other libs), but still leaves incorrect cases likeSql
instead ofSQL
for the initialism ‘structured query language’ (where documentation is largely using “SQL”).What I would expect is the implicit ID for
Foo
becomesFooID
… allfooId
columns becomefooID
.Moving from ‘ID’ to ‘Id’ is losing valuable casing information & if it weren’t important, we wouldn’t be bothering with upper case letters at all in English (& other languages with bicameral scripts).
The text was updated successfully, but these errors were encountered: