feat: migrations at the resource layer. #30
Merged
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.
Overview
RequestMigrations v2 introduces a type-based migration system that replaces the original handler-based approach. Instead of defining migrations per API handler (e.g.,
createUserRequestMigration), migrations are now defined per Go type (e.g.,AddressMigrationfor theAddressstruct).Key Features
Design
The system builds a type dependency graph to handle nested structs and cycles, applying migrations recursively through the object graph.
Internal Pivot
While the public API is version-centric, the internal storage is now type-centric (
map[reflect.Type]map[string]TypeMigration), allowing for efficient graph construction.Usage
Status