Guy Tsitsiashvili

@fishcharlie hi, I'd like to continue working on this feature, and extend it to support item method types as well, yet the codebase is a little 'overwhelming' I'd say 😅....

I had a similar issue using react, the problem is that amplify has a bug when importing ESM modules and not CommonJS. The fix I found recently was aliasing ```runtimeConfig.browser```...

hmm... I'm actually not familiar with ``config.resolve.alias`` being an array so my intuitive suggestion would be replacing ``` { './runtimeConfig': './runtimeConfig.browser' }, ```` with ``` { find: "./runtimeConfig", replacement: "./runtimeConfig.browser",...

@lostdesign can you let me know if the problem was fixed?

Pydantic V2 introduced [`TypeAdapter`](https://docs.pydantic.dev/latest/api/type_adapter/) and annotated types with validators. Using `RootModel` feels a little anti-pattern in V2, maybe consider working with `TypeAdapter` more often, In your example (and given you...

That's seems like a deep problem, implementing an iterative migration might be daunting. I can recommend custom validation for this case. Assuming your data is saved somewhat like this ```jsonc...

Hi @roman-right, unfortunately I've found that my solution isn't all-inclusive and there are many edge cases, I'm drafting this PR and will work on it.

@roman-right I hope that's enough for a fix. I tested the type inference in VSCode and it seems to work, is there maybe a test I can implement to future-proof...

Great news, thanks.