Summary: 111 instances, 81 unique

Text	Count
// TODO: Dispatch/notify error if we can't erase to any model? Would imply an error in JSON decoding,	1
// TODO: Handle errors from delete, and convert to async	1
// TODO: implementation details - use request.options.limit.	1
// TODO: Move this metadata to plugin options. All other request has the metadata	1
// TODO: transferAcceleration should be in pluginOptions	1
// TODO: implement	1
/// TODO: Implement testGetBlogThenFetchPostsThenFetchComments	1
// TODO: Delete Team should not be necessary, cascade delete should delete the team when deleting the project.	4
// TODO find better way to test `Binding` equality	1
/// TODO: Include testGetPostThenFetchBlogAndComment when nested model lazy loading is implemented	1
// TODO: Error handling	1
// TODO: Implement tagging functionality, got 403 on tagging using below code	1
// TODO verify no retain cycle	1
// TODO: Subscriptions always require an `owner` field.	1
// TODO: Refactor this so that it's clear that the storage engine is not responsible for setting the version	1
// TODO: some error mapping	3
// TODO: Implement the test below	1
// TODO: to be implemented	1
// TODO: Add conveinence to queryPredicate where we have a list of items, to be all or'ed	1
//TODO implement code	6
// TODO: missing unit tests for pause resume and cancel. do we create a mock of the StorageTaskReference?	1
//TODO: Retrieve this version from a centralized location:	1
// TODO: https://github.com/aws-amplify/amplify-ios/issues/695	1
// TODO: missing unit tets for pause resume and cancel. do we create a mock of the StorageTaskReference?	1
// TODO: first time run fails, hm	1
//TODO: Parse error from the receive completion to use as an input into getting retry advice.	1
/// TODO: Replace with AmplifyTestCommon's DataStore's geneated model	1
// TODO: Make this private once we get a mutation flow that passes the type of mutation as needed	1
// TODO: assert on version 3 once updates are working	1
// TODO content type messaging	1
/// TODO: Include testGetPostThenLoadPostEditors when nested model lazy loading is implemented	1
// TODO: remove this https://github.com/aws-amplify/amplify-ios/issues/75	1
// TODO: dispatch Hub event	1
// TODO: Verify with the team that terminating a subscription after failing to decode/cast one	1
// TODO: Should the queried project eager load the has-one team?	1
// TODO: https://github.com/aws-amplify/amplify-ios/issues/695	1
Either do not specify a contentType and it will default to TODO or specify a correct MIME type like X, Y, Z	1
// TODO: We shouldn't be inspecting state, we should be using granular enough states to	1
// && lhs.team == rhs.team // TODO: Should the Project have the team?	1
// TODO: check if there is a limit on total number of properties	1
// TODO: revist this, this is exposing internal implementation	1
// TODO: Split these tests into separate suites	1
// TODO: Extract context and fill out better error handling	1
// TODO how to handle associations of type "many" (i.e. cascade save)?	1
// TODO assert	1
// TODO: test pause, resume, canel, etc.	2
// TODO: Remove in the future when the plugin no longer depends on the SDK and have addressed this problem.	2
// TODO serialize result and create a new instance of the model	1
// TODO: Add target for SyncEngine system to help prevent thread explosion and increase performance	1
/// TODO:  Include testSaveCommentAndGetPostWithComments test when nested model lazy loading is implemented	1
// TODO: Is this the right command to run to generate models?	1
// TODO benchmark whether a SELECT FROM FOO WHERE ID IN (1, 2, 3...) performs measurably	1
// TODO: Retry query on error	1
// TODO: Handle errors from delete	1
// TODO: This should be an AsynchronousOperation, not a semaphore-waited block	1
// TODO: No need to add the `team` into the project, it is using explicit field `project1V2TeamId`	2
// TODO: validate that metadata values are within a certain size.	1
// TODO: Resolve with an appropriate state machine notification	1
// TODO: Differentiate between save & update	1
// TODO: more upper limit validation here due to some iOS background processing limitations	1
// TODO: testValidateMetadataValuesTooLarge	2
// TODO: refactor - move each the publisher constructions to its own utility method for readability of the	1
// TODO: Remove exposing AWSPinpointEvent	1
// TODO: Handle errors from mutation event creation	1
// TODO handle total count	1
// TODO: Refactor this into a proper request/result where the result includes metadata like the derived	2
// TODO: Upates are not working due to CLI provisioning issue. the Update mutation is missing the `id`	1
// TODO: thread safety: everything has to be locked down	1
// TODO: Not implemented.	14
// TODO handle modelName casing (convert to camelCase)	2
//TODO: Update to use TimeInterval.milliseconds when it is pushed to main branch	1
// TODO: service error, check string?	1
// TODO: Should the queried project eager load the has-one team?	1
// TODO: Refactor this into separate test suites	1
// TODO load schema from JSON when this it not overridden by specific models	1
// TODO: turn async https://github.com/aws-amplify/amplify-ios/issues/73	1
// TODO query name could be useful for the message, but re-creating it here is not great	1
/// TODO document this and change it to work in a way that these functions are not	1
// TODO: Can this actually happen on an incoming sync?	1
// TODO: possibly after understanding content-type	1
// TODO: Deleting the comment should not be necessary. Cascade delete is not working	2