Sam Chung

+1 on the need to be able to introspect if possible. I contribute to [@asteasolutions/zod-to-openapi](https://github.com/asteasolutions/zod-to-openapi) and my own [zod-openapi](https://github.com/samchungy/zod-openapi) and we rely on being able to grab the options to...

I think the workarounds are sufficient here. I don't think any of the other string validators would accept an empty string as a valid option. You wouldn't consider an empty...

> Solutions with `transform` and `preprocess` make code less appealing and boilerplate code ( two times nullish() & string() etc.) > > I would like something like this: > >...

I don't think you follow. An empty string !== datetime so you would never have any option in datetime like that. Realistically if you wanted something it'd look more like:...

>Another idea is to add a method .empty() to ZodString which returns a ZodEffects instance. > >``` >z.string().empty(null); // => ZodEffects >``` I low-key love this. So elegant. But the...

We could accept both kinds of inputs?

Yeah I understand the opinions in https://github.com/colinhacks/zod/issues/273. It could very easily lead to anti-patterns however I can also see the benefits of adding a meta field. At the moment I'm...

Hey! Thanks for the PR! I love the attempt I think a slightly simpler option may be just to create the files under our `base` folder section. I think that...

I think including extensions.json in the git makes sense. The main reason the vscode folder is ignored is mostly to stop user settings from constantly being committed, however, this isn't...

Should we log the parameters we call the checkRun with if we fail? I suspect the only way will be a bit of trial and error against the checkrun API...