Skip to content

fix(bindx-form): handle 'double precision' column type#13

Merged
vparys merged 1 commit intomainfrom
fix/double-precision-column-type
Apr 8, 2026
Merged

fix(bindx-form): handle 'double precision' column type#13
vparys merged 1 commit intomainfrom
fix/double-precision-column-type

Conversation

@vparys
Copy link
Copy Markdown
Member

@vparys vparys commented Apr 8, 2026

Summary

  • Contember schema generates 'double precision' as the columnType for doubleColumn() fields, but columnTypeAliases only mapped 'double''Double'
  • This caused the default string handler to be used, sending string values (e.g. "500") to the GraphQL API which rejects them for Float fields
  • Added 'double precision': 'Double' to the alias map

Test plan

  • Verified in NPI admin — creating a session with participantFee (doubleColumn) now sends a number instead of a string

@vparys vparys force-pushed the fix/double-precision-column-type branch 2 times, most recently from d994f15 to e345047 Compare April 8, 2026 11:30
…type strings

Generator now emits normalized ColumnType values ('String', 'Integer',
'Double', etc.) instead of raw PostgreSQL types ('text', 'double
precision', 'boolean'). This removes the need for the columnTypeAliases
map in useFormInputHandler and prevents the class of bugs where a
PostgreSQL alias was missing.
@vparys vparys force-pushed the fix/double-precision-column-type branch from e345047 to 29740ad Compare April 8, 2026 11:33
@vparys vparys merged commit 642cfce into main Apr 8, 2026
3 checks passed
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.

1 participant