Normalize doesn't seem to do anything with aot: false

[danieljvdm]

What version of Elysia is running?

1.2.10

What steps can reproduce the bug?

In a cloudflare worker environment with aot: false, the default behavior of normalizing responses seems to be broken.

For:

const TestType = t.Object({
  foo: t.String(),
});

const route = new Elysia({ aot: false })
  .get(
    '/:id',
    async () => {


      const test = {
        foo: 'bar',
        baz: 'qux',
      };

      return test;
    },
    {
      response: TestType,
    },
  );

We get:

{
  "type": "validation",
  "on": "response",
  "summary": "Property 'baz' should not be provided",
  "property": "/baz",
  "message": "Unexpected property",
  "expected": {
    "foo": ""
  },
  "found": {
    "foo": "bar",
    "baz": "qux"
  },
  "errors": [
    {
      "type": 42,
      "schema": {
        "type": "object",
        "properties": {
          "foo": {
            "type": "string"
          }
        },
        "required": [
          "foo"
        ],
        "additionalProperties": false
      },
      "path": "/baz",
      "value": "qux",
      "message": "Unexpected property",
      "errors": [],
      "summary": "Property 'baz' should not be provided"
    }
  ]
}

[danieljvdm]

If we import import { Value } from '@sinclair/typebox/value';

We can manually clean the response and things work as expected.

const cleanedRecipe = Value.Clean(RecipeDetailDTO, recipe);

[danieljvdm]

Another incredibly strange datapoint.... I have this route handler in the same Elysia instance as the above example (though the real code was swapped out for the foo/bar example)

  .get(
    '',
    async ({ query, recipeService }) => {
      const search = query.search;

      const recipes = await recipeService.getRecipes({
        searchQuery: search,
        filter: { idIn: query.idSearch ? query.idIn ?? [] : undefined },
      });
      return recipes;
    },
    {
      response: RecipeListDTO,
      query: t.Optional(
        t.Object({
          search: t.Optional(t.String()),
          idSearch: t.Optional(t.Boolean()),
          idIn: t.Optional(t.Array(t.String())),
        }),
      ),
    },
  )

In this code, I don't get a validation error on recipes (even though it's returning way more data than the DTO is asking for) and it also isn't normalized... literally nothing happens. And this is in the same instance as I get a validation error on my too-big object...

[yvvki]

This behavior is prevalent on the html plugin too where the autoDetect option, which triggers mapResponses, would not do anything.

[danieljvdm]

Additionally I just realized that it's breaking automatic parsing of array string parameters:

query: t.Optional(
  t.Object({
    idIn: t.Optional(t.Array(t.String())),
  }),
),

  \"summary\": \"Property 'idIn' should be one of: 'ArrayString', 'array'\",
  \"property\": \"/idIn\",
  \"message\": \"Expected union value\",
  \"expected\": {},
  \"found\": {
    \"idIn\": \"01946d00-3d17-717e-b4e3-81844d710af7\",
  },

This was working fine before i switched to aot: false/serverless

[danieljvdm]

I'm curious if there's any plans to address issues like that seem to affect aot: false. I'm getting close to having to drop Elysia (though I love it) due to a lot of issues like this stacking up