Refactor: Ensure correct type for PostgresDsn instantiation#69
Merged
HosseinNejatiJavaremi merged 1 commit intoSyntaxArc:masterfrom Aug 16, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR resolves a
PydanticSerializationUnexpectedValuewarning that occurs when building the PostgreSQL connection DSN.The Problem
The code was assigning a raw formatted string to a field that is typed as
pydantic.networks.PostgresDsn. This caused Pydantic to raise the following warning during serialization:The Solution
The fix is to explicitly instantiate the
PostgresDsnclass with the connection string. This ensures that the field holds an object of the correct type, leverages Pydantic's validation, and silences the warning.