Hartmut

thx, all tests pass!

~~can confirm above issue for _camelCase_ property names, too (as @nilswieber referred to) Manually defining the `@JsonProperty("camelCase")` works as well as a workaround. thx @PeterVanco~~ Edit: wrong statement, see comments...

after some debugging it looks like `com.fasterxml.jackson.databind.introspect.POJOPropertiesCollector#collectAll` resolves fields for the data class with the correct case (`Name`) - but then in addition resolves the prop again from the getter.....

I mentioned above that the same issue occurs for `camelCase` which is wrong. BUT it does occur for `cCase` (1 leading lowercase char followed by 1..* Uppercase). Following my previous...

@cowtowncoder @apatrida what would be the logical right thing to do here? I would be happy to contribute but I'm not quite sure where / how to approach. Could you...

Hi, would anyone be able to provide some guidance - I have created unit tests and spent a lot of time debugging - but I wasn't able to really understand...

@cowtowncoder, many thanks for your replies and guidance. I do understand above statement RE things being ..complicated 😃 - I've already had spent quite some time debugging without really getting...

hmm is the vercel-builder even still used/needed for nuxt3? 🤔 https://github.com/pi0/nuxt-on-the-edge I can see using `NITRO_PRESET=vercel-edge` generates `.vercel/output/` incl. `.vercel/output/config.json` - but missing the config for _Vercel Image Optimisation_ https://github.com/vercel/examples/tree/main/build-output-api/image-optimization...

> I'm working on a hook to use from image module extending config. is the hook part done/merged already? I thought I've had seen the relevant PR 🤔

🚀 I can confirm this seems to be working fine with e.g. `nuxt.config.ts` ```ts import { defineNuxtConfig } from 'nuxt' import { defineNitroConfig } from 'nitropack' // https://v3.nuxtjs.org/api/configuration/nuxt.config export default...