Skip to content

fix: Pydantic Factory alias generation from version 2.11 #718

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

sandre35
Copy link

Description

  • This PR aims to fix alias generation. This is due to populate_by_name config attribute being deprecated by Pydantic from version 2.11

Closes

Closes #717

@sandre35 sandre35 requested a review from guacs as a code owner June 27, 2025 09:59
@sandre35 sandre35 changed the title Pydantic Factory alias generation from version 2.11 fix: Pydantic Factory alias generation from version 2.11 Jun 27, 2025
Copy link
Collaborator

@adhtruong adhtruong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would be a backwards breaking change. Can both alias be support both names until a major release is made to explicitly drop support for current config name?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What requires the lock file to be changed for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: Pydantic factories using deprecated "populate_by_name" to determine alias usage
2 participants