-
-
Notifications
You must be signed in to change notification settings - Fork 84
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
I have a very simple bug : when checking out the content of my FDW Stripe Subscriptions table, I don't have the same content as what the Stripe API's outputs. For the moment my wrapper is connected to Stripe in test mode.
To Reproduce
So for example for me this happens with the JSONB content of the attrs column
I'll have the following data with Stripe's API :
"cancel_at": 1736151465,
"cancel_at_period_end": true,
"canceled_at": 1733769670,
And in Supabase's Stripe FDW , in a different order :
"cancel_at_period_end": false,
"cancel_at": null,
"canceled_at": null,
Expected behavior
I expect the data in the FDW table to mirror what Stripe's API outputs
Screenshots
If applicable, add screenshots to help explain your problem.
System information
I'm using Supabase Cloud's offering, with Postgres 15.6.1.146, Wrappers version 0.4.2
Thanks!
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working