A
arktype•2mo ago
mshafir

How to combine multiple configure() calls

I noticed that if I call configure multiple times each next call wipes out the previous metadata. Here's a test example 
test("arktype config", () => {
    const t = type("string")
        .configure({ description: "a test" })
        .configure({ alias: "cool" });
    expect(t.toJSON()).toMatchInlineSnapshot(`
        {
          "domain": "string",
          "meta": {
            "alias": "cool",
          },
        }
    `);
});
test("arktype config", () => {
    const t = type("string")
        .configure({ description: "a test" })
        .configure({ alias: "cool" });
    expect(t.toJSON()).toMatchInlineSnapshot(`
        {
          "domain": "string",
          "meta": {
            "alias": "cool",
          },
        }
    `);
});
Using .describe() has the same results. Notice that the meta only has the alias, not the description. Is there a way to instead have configure chain the request so it doesn't override prior metadata? I know in theory it could all happen in one configure, but in my codebase there are multiple layers so that in some cases I want to build on another type and just add some metadata to it.
3 Replies
ssalbdivad
ssalbdivad•2mo ago
You can use .internal.withMeta(existing => ({...existing, alias: "cool"})). you may want to create a wrapper that does this then just return the original type since this version will lose the narrowed inference I'm actually not sure why we're currently not exposing some version of that signature through configure, but I will add it for next release. One important difference to note until I do publish the new configure though- withMeta only applies the metadata to the root type node e.g. a union, an intersection or some primitive node like domain. configure applies the new metadata to all shallow nodes (i.e. up until you get to a prop).
mshafir
mshafirOP•2mo ago
got it, thanks! and amazing how fast you replied
ssalbdivad
ssalbdivad•2mo ago

Did you find this page helpful?