Skip to content

fix: Let column names not invalidate Go field names #1840

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

Closed
wants to merge 1 commit into from

Conversation

rollulus
Copy link
Contributor

@rollulus rollulus commented Sep 8, 2022

Column names are less restricted than Go struct field names, which should be proper Go identifiers. Hence, column names cannot be translated directly into field names. This commit tries to address this.

Characters in column names that do not qualify as a Go identifier are stripped. The title casing as applied to underscores is applied to stripped characters.

@rollulus
Copy link
Contributor Author

rollulus commented Sep 8, 2022

I wasn't sure about the e2e test naming convention. Also: thanks for this project!

@rollulus rollulus force-pushed the fix/field-names branch 2 times, most recently from 74f5523 to 629913d Compare September 9, 2022 10:01
Column names are less restricted than Go struct field names, which
should be proper Go identifiers. Hence, column names cannot be
translated directly into field names. This commit tries to address
this.

Characters in column names that do not qualify as a Go identifier
are stripped. The title casing as applied to underscores is applied
to stripped characters.
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

Successfully merging this pull request may close these issues.

2 participants