Fix ID/UUID field serialization and Pydantic type mapping (#40) #41
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.
Issue: #40
Problem
Django models using
UUIDField,UUIDAutoField, orForeignKeywith a UUID PK were not properly serialized in lazy-ninja.Pydantic schemas expected
intorstr, causing validation errors when UUIDs were returned directly.Solution
get_pydantic_typeto checkUUIDFieldbeforeAutoField, ensuringUUIDAutoFieldmaps tostr.serialize_model_instanceto convertUUIDFieldandForeignKey(to UUID PKs) into strings.convert_foreign_keysto handle both integer and string PKs.parse_model_int, a new helper that converts string path parameters into the correct type for the model’s PK in CRUD routes.Impact
DEFAULT_AUTO_FIELD = "core.fields.UUIDAutoField".AutoFieldPKs.Example
Closes #40