bradleat
bradleat
I'll work on it next Tuesday then.
@FabianLars I opened a PR with the changes. Not sure if that's the right process here. But just wanted comments.
I think we could also save some type by only running the transform if typia is actually imported. Right now it looks like any import from the typia package (like...
I'm so confused why you can't just detect the interesction of a string and another type and then only check for it being a string. Nobody wants to do ```...
Like why not detect the `string & {}` pattern here: ``` // ESCAPE WHEN ONLY CONSTANT TYPES EXIST if ( atomics.size + constants.length + arrays.size > 1 || individuals.length +...
Related to LLM structured outputs, I find that when prompting I often want to use the jsdoc comment for a type in the prompt. Can typia add a misc method...
> I feel like this could easily be turned into a security risk for various injection attacks. I would say this would need a lot of investigation before doing type...
Just watned to plus one this. I have some code where I have to manually construct a validator for each side of the union otherwise typia fails.
@samchon idk why you insist on fighting your community on this. you've created a great tool and @MatAtBread has a reasonable solution to everyone's problem. please adopt it.
Just bumping this one! This will make it easy to create plugins that respect attributes from import statements.