-
Notifications
You must be signed in to change notification settings - Fork 260
Open
Labels
datastoreIssues related to the DataStore CategoryIssues related to the DataStore Categoryfeature-parityA request for a feature that is fully or partially available on another platform (JS, iOS, Android)A request for a feature that is fully or partially available on another platform (JS, iOS, Android)feature-requestA request for a new feature or an enhancement to an existing API or category.A request for a new feature or an enhancement to an existing API or category.requires-ios-fixThis issue is the result of an underlying Amplify iOS issue that needs to be fixed.This issue is the result of an underlying Amplify iOS issue that needs to be fixed.
Description
Description
I have schema like this
type Entry @model {
id: ID!
draftRecordID: ID @index
}
With Amplify GraphQL, I can set draftRecordID to null.
With Amplify DataStore, I can not, even with
entry.copyWithModelFieldValues(draftRecordID: const ModelFieldValue.value(null));
Categories
- Analytics
- API (REST)
- API (GraphQL)
- Auth
- Authenticator
- DataStore
- Notifications (Push)
- Storage
Steps to Reproduce
Create schema with a nullable String index. Set the String index field to a value. Attempt to remove that value by setting it to null
.
Screenshots
No response
Platforms
- iOS
- Android
- Web
- macOS
- Windows
- Linux
Flutter Version
3.19.1
Amplify Flutter Version
1.6.1
Deployment Method
Amplify CLI
Schema
type Entry {
id: ID!
draftRecordID: ID @index
}
Metadata
Metadata
Assignees
Labels
datastoreIssues related to the DataStore CategoryIssues related to the DataStore Categoryfeature-parityA request for a feature that is fully or partially available on another platform (JS, iOS, Android)A request for a feature that is fully or partially available on another platform (JS, iOS, Android)feature-requestA request for a new feature or an enhancement to an existing API or category.A request for a new feature or an enhancement to an existing API or category.requires-ios-fixThis issue is the result of an underlying Amplify iOS issue that needs to be fixed.This issue is the result of an underlying Amplify iOS issue that needs to be fixed.