Bogeychan

@omarkhatibco, I already tried it on elysia `1.1.3` but it doesn't work: https://github.com/bogeychan/elysia-logger/blob/6d9cbe4ddc0767ff0389243d2ab74b97a072ff86/tests/error.test.ts#L68

all good, I sometimes forget stuff too 😅 There is an issue on elysia's side blocking the progress of this issue (it is mentioned under additional information). If you need...

this has been fixed in `[email protected]`

@SaltyAom, ~~It still converts the cookie value to `number` even though I specified `t.String` as the type~~ nvm, bun installed wrong version 😭

BUT i got an error when passing `123`: ```json { "type": "validation", "on": "cookie", "property": "/hello", "message": "Expected string", "expected": { "hello": "" }, "found": { "hello": 123 }, "errors":...

same bug with `new Elysia({ aot: false })`

@SaltyAom, yes, it occurs on `1.0.23`, you have to pass number instead of some char sequence:  and the handler has this schema: ```ts { cookie: t.Cookie({ hello: t.String() })...

Like this test doesn't pass... ```ts import { describe, it, expect } from "bun:test"; import { Elysia, t } from "elysia"; describe("Cookie", () => { it("???", async () => {...

I'd prefer no automatic parsing and use `string` as default because you end up with a lot of code like this doing type checking/casting and unnecessary `number` parsing could affect...

2. I agree with these people; i don't like side effects too (including cookie-parsing) You won't end up with this weird behavior if you only allow `string` by default (instead...