fix: remove explicit fieldName override to restore snake_case column …#27
Merged
Conversation
…naming The chargebeeCustomerId field in userSchema and orgSchema had a hardcoded fieldName: "chargebeeCustomerId" that suppressed Better Auth's built-in camelCase→snake_case mapping, causing the column to be created as chargebeeCustomerId instead of chargebee_customer_id. Removing the override lets Better Auth's automatic mapping apply correctly. Bumps version to v1.0.0-beta.5. Made-with: Cursor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
cb-karthikp
approved these changes
Mar 18, 2026
cb-muthiahm
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v1.0.0-beta.5 (2026-03-18)
Bug:
chargebeeCustomerIdcolumn naming. The field definition in bothuserSchemaandorgSchemahad an explicitfieldName: "chargebeeCustomerId"that overrode Better Auth's built-in camelCase→snake_case mapping, causing the column to be created aschargebeeCustomerIdinstead of the expectedchargebee_customer_id. The explicit override has been removed so Better Auth's automatic mapping applies correctly.