fix: Send correct field_meta to avoid over nesting

[Vegemash]

Checklist

• [ ] New code has 100% test coverage
• [ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
• [ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
• [x] Pre-Commit Checks were ran and passed
• [x] Tests were ran and passed

Description

• Avoid passing parent field_meta incorrectly for collection coverage

Close Issue(s)

• 526

[Vegemash]

@adhtruong

Commit history and state seems to be out of sync with main. Can you sync up with main please?

rebased

[sam-or]

Any chance we can get this in soon @guacs?

[guacs]

Any chance we can get this in soon @guacs?

Yupp, I'll be merging this and making a new patch release if the tests all pass.

[guacs]

Hm...the failing test doesn't seem to be related to the changes made here. In fact, it looks like a possible bug in pydantic.

[guacs]

Okay, so this is known bug in pydantic. However, it was fixed and a patch version was released, but we seem to be specifically installing v1.10.10 of pydantic as introduced in #389. Was there any specific reason for this, @adhtruong? Or can we specify only the minor version so that we always install the latest version in CI?

[adhtruong]

Hi @guacs, looking at that PR I think I copied what's there. Specifying patch versions keep things deterministic but should be safe to specify minor version only to unblock more easily.

SQLA versioning strategy should be aligned but happy for that to be a separate PR.

Thanks for the work on this @Vegemash !

[Vegemash]

@guacs @adhtruong #561 pydantic bump PR

[guacs]

@all-contributors add @Vegemash for code

[allcontributors[bot]]

@guacs

I've put up a pull request to add @Vegemash! :tada:

[github-actions[bot]]

Documentation preview will be available shortly at https://litestar-org.github.io/polyfactory-docs-preview/527