T
tRPC

SuperJSON is wrapping results in type with keys "json" and "meta"

SuperJSON is wrapping results in type with keys "json" and "meta"

Jjimfilippou
View on Discord
5/10/2023
How can I modify the transformer in SuperJSON library to only return the "json" property and ignore the "meta" property during serialization? The current behavior of the library wraps the results in the SuperJSONResult interface, but I want to access only the "json" property after serialization. 
interface SuperJSONResult {
    json: JSONValue;
    meta?: {
        values?: MinimisedTree<TypeAnnotation>;
        referentialEqualities?: ReferentialEqualityAnnotations;
    };
}
interface SuperJSONResult {
    json: JSONValue;
    meta?: {
        values?: MinimisedTree<TypeAnnotation>;
        referentialEqualities?: ReferentialEqualityAnnotations;
    };
}
This is my current code 
const t = initTRPC.context<inferAsyncReturnType<typeof createContext>>().create({
  transformer: {
    serialize: SuperJSON.serialize,
    deserialize: SuperJSON.deserialize,
  },
});
const t = initTRPC.context<inferAsyncReturnType<typeof createContext>>().create({
  transformer: {
    serialize: SuperJSON.serialize,
    deserialize: SuperJSON.deserialize,
  },
});
Nnlucas
View on Discord
5/10/2023
superjson needs that to work, if you don't want it then you should remove superjson, but then types like dates will be strings

Looking for more? Join the community!

T
tRPC

SuperJSON is wrapping results in type with keys "json" and "meta"

Join Server
Recommended Posts
Caching(?) previous data until query returns new datawhen I update my useQuery inputs with new filters it instantly sets the data to `undefined` while thHow to upload file not use S3 Next js? Please, examplefile: course.router.ts / import { CourseSchema } from "~/schema/post.schema"; import { createTRPChow can i send a request to specific route in trpc server, after mutation ?i am using trpc with next js ,Help in deploymentHey all, I am building an app which is having a 1 . vite-react frontend 2 . trpc-standalone how to persist the query client?I want to persist the trpc query client cache, but don't want to create a new query client, I want tHow to infer type of a nested object from app router output?I have a tRPC router than returns a nested object through a db query. It looks like this: ```ts ILe