[Feature?]: When seroval fails to serialize an object, treat it as json

[huseeiin]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Summary 💡

const getProcess = query(async () => {
  "use server";

  return process;
}, "process");

const process = createAsync(() => getProcess());

return (
  <Suspense fallback={<p>Loading...</p>}>{JSON.stringify(process())}</Suspense>
);

seroval doesn't know how to serialize process. how about treat something that can't be serialized as normal json?

Examples 🌈

if the solution is implemented, this is how it'd work under the hood:

const getProcess = query(async () => {
  "use server";

  return JSON.parse(JSON.stringify(process));
}, "process");

const process = createAsync(() => getProcess());

return (
  <Suspense fallback={<p>Loading...</p>}>{JSON.stringify(process())}</Suspense>
);

Motivation 🔦

this allows for more room for other types of values

[lxsmnsyc]

This is too dangerous. Majority of process info is sensitive. Are you really sure you want to serialize this?

Regardless, this won't be supported like any other "unserializable" objects.

[huseeiin]

This is too dangerous. Majority of process info is sensitive. Are you really sure you want to serialize this?

Regardless, this won't be supported like any other "unserializable" objects.

oh, regarding that, no, i of course don't wanna serialize process. this is just an example.

[atilafassina]

I agree that this is too dangerous to be a default, but potential user-base customizations of Seroval are being discussed in #1474

So I'm closing this one and once we get to an architecture that Seroval may allow for extensibility, this can be done separately

@huseeiin , please join the discussion there with your use-case :)