chore: Remove unused Amplify managed table & RDS transformer & generator #3063
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.
Description of changes
Removes the SQL and Amplify-managed DDB table logic from
@aws-amplify/graphql-model-transformer
:This PR is not technically a prerequisite for it, but I'm doing this as part of the work for #3006.
Although the functional changes in this PR are limited to
@aws-amplify/graphql-model-transformer
, it has broad-reaching implications for tests elsewhere, since we make heavy use of snapshot tests and the generated resources will no longer contain SQL or Amplify-managed resolvers. Thus, this PR touches or deletes 91(!) files. This PR simply removes RDS & Amplify-managed DDB tests.Finally, removing the RDS tests reduced coverage in some cases; those coverage thresholds have been adjusted down accordingly.
Issue #, if available
#3006
Description of how you validated changes
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.