You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Thanks for reporting this issue. I cannot reproduce this error, could you provide more details or double check if your're accessing the same Stripe account?
Bug report
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 :
And in Supabase's Stripe FDW , in a different order :
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!
The text was updated successfully, but these errors were encountered: