feat: support field-level resolvers in the model #627
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.
Problem
Issue number, if available:
aws-amplify/amplify-category-api#3306
Changes
This pull request introduces support for field-level resolvers (handlers) in the
@aws-amplify/data-schemapackage, allowing developers to attach custom logic directly to individual fields in their models. The implementation includes updates to the schema builder API, schema processing logic, and related tests and documentation.Field-level handler support:
.handler()method to theModelFieldbuilder, enabling the attachment of field-level resolvers (handlers) to fields. This is reflected in both the type definitions and the runtime implementation (ModelField.ts).Corresponding docs PR, if applicable:
Validation
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.