Joseph Mearman

Sorry I missed out, then including it alongside other nodes in an existing kit. Some of them require a bit of tinkering.

This ^ and my indecision about what to include in code nodes vs board mechanics vs kits, as well what I was thinking about regarding the "board signatures" makes me...

well initially it's spawned from wondering about [passing a board that has a certain signature](https://github.com/orgs/breadboard-ai/discussions/1195) but I think it could extend to the underlying logic of the node. If you...

so for example updating the schema type to be: ``` type Schema = { type: "string" | "boolean" | "object" } ```

> "number" | "array" -- yup, got it. We'll ideally integer too as it's being used for input validation

I'm assuming they're not all currently being driven by the schema package?

I think I might be poorly differentiating an issue with the example values and an issue with the default values. There's also the runner and harness. I only remembered after...

It is still a thing though I'm not sure if it's actually supported by breadboard types yet

this is on the actual TS types. not in the UI

here's a good example https://github.com/breadboard-ai/breadboard/blob/main/packages/breadboard-web/src/boards/open-alex-entity-search-list.ts#L37-L42