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
Not only would these functions be helpful for existing projects, they would also be helpful for creating simpler examples for teaching kysely json utilities.
The text was updated successfully, but these errors were encountered:
We'd have to keep adding the JSON functionality to every function if we did this.
We should rather pull out the json reference code to a separate helper. ref could still have it as it's a very common case. But we could also have something like:
I think eb.val(json) is blocked by #1130 - the under-the-hood serialization element of it. The gist of it was JSON.stringify by default, but allow custom logic override - e.g. running superjson, omitting/redacting things, etc.
Discussed in https://discord.com/channels/890118421587578920/1315878442281209907/1315878442281209907
Currently, all the json utilities expect a column. While it is possible to use these utilities via CTEs:
It would be better if they had built-in support via:
Not only would these functions be helpful for existing projects, they would also be helpful for creating simpler examples for teaching kysely json utilities.
The text was updated successfully, but these errors were encountered: