Michał Orkisz

This seems to be a working temporary fix (you can test it with console.log). Just paste the below code to \api\src\controllers\assets.ts:192 ``` stream.on('end', () => { if (!res.headersSent) { res.status(200).send();...

@ryansolid Next.js has a nice [ReadonlyURLSearchParams](https://github.com/vercel/next.js/blob/beeefdb1120b1d857b2c89d391cf84ffa3f0e2c0/packages/next/navigation-types/compat/navigation.d.ts). I think `useSearchParams` should return a similar object. Current implementation only returns the last value if there are multiple keys with the same name....

> Do you know what `uniqueItems` work when the element type is object or another array? I did some research, and indeed it seems that `uniqueItems` should validate the array...

I also noticed a small issue with the current `uniqueItems` implementation. When false is passed into `tags.UniqueItems`, empty arrays and arrays with only one item are considered invalid, even though...

All good. Thank you for your amazing libraries.

Thanks for quick response. When `is()` is used, both `TypedQuery` and `TypedBody` return: ```ts interface _ { message: string; error: "Bad Request"; statusCode: 400; } ``` I think `TypedParam` should...

> any update or progress on this PR? I can't be arsed to write the tests, but I have published the patch on [npm](https://www.npmjs.com/package/@xxmichas/ncc)

@bluebill1049 what would it take to support flat (primitive) arrays in useFieldArray? If direct support isn’t possible, could there be a special key (similar to id) that represents the primitive...