1
Can we support opt out for `arbitrary_precision` feature in the `serde_json` dependency?
Source: supabase/supabase#51207 · opened by @PookieBuns
Hi I am trying to use ETL as a embedded cdc library for my application However, I was just hit with a serde_json bug The reason was because ETL enable aribitrary_precision in serde_json, which in turn breaks my application serde json deserialization because compiling uses the superset of features based on resolver 3.
I was wondering
A. If arbitrary_precision is required for ETL to work properly and a must have
B. If A is not true, can we have support consumers opting out of it through a default feature like serde_json_arbitrary_precision
Thanks!
I was wondering
A. If arbitrary_precision is required for ETL to work properly and a must have
B. If A is not true, can we have support consumers opting out of it through a default feature like serde_json_arbitrary_precision
Thanks!
No pledges yet. Be the first to back this.
Comments
Similar requests
Support Custom Phone Authentication Providers
1 vote · 0 comments
feat(auth): use argon2id as default algorithm for GenerateFromPassword
3 votes · 0 comments
Bump supabase-js from v1 to v2
1 vote · 0 comments
Realtime search capability
2 votes · 0 comments
Bubble up errors on dependency graph failures
3 votes · 0 comments
No comments yet.