Andrew Truong

For the original case, this is particularly well supported and current behaviour is correct. As workaround, could override `get_field_value` and then check `FieldMeta.annnotation` and map this type explicitly. Some thing...

Thanks for reporting! I'd recommend your workaround used to not use new syntax for now. PRs welcome to fix. Internally this is not being properly unwrapped in all places yet...

Apologies - realised created another conflict for here when merging other things. Can this be updated again please?

https://github.com/all-contributors add @Rub1kCube for code Thanks for the work on this!

Change looks good! Can you look at the failing tests and update please?

https://github.com/all-contributors add @priyankc for bugs

> [#568](https://github.com/litestar-org/polyfactory/issues/568) ? Hi @Goldziher, PRs welcome for this but unlikely to make one myself for this. Using v3 to remove deprecated functionality and change some defaults. If adding new...

Picking up work on this again now I have more free time. Remaining steps, 1. Merge docs PR https://github.com/litestar-org/polyfactory/pull/704 2. Revert changes for `SQLAlchemyFactory.__set_association_proxy__`. This has had some strange behaviour...

Hi @mjmaurer , Looks like this currently isn't possible but PRs welcome to fix. Couple of potential workarounds - Set this at the field level. - Create a separate factory...

There is a feature in polyfactory to guard against recursive relationships where possible but this is not applied to explicitly defined factory as fields. Potential workaround would be `__set_as_default_type__` [docs...