aws-amplify
fix: datastore clarify api boundary with api/cli
Description of changes:
Clarify that Amplify Datastore API is not the same as GraphQL. Also clarify that Auth rules of Datastore are a subset of what is offered in CLI. This distinction is not clear in our docs, which caused a customer to lose a lot of time thinking that certain features were present in Datastore....
Related GitHub issue #, if available:
https://github.com/aws-amplify/amplify-flutter/issues/3388
Instructions
If this PR should not be merged upon approval for any reason, please submit as a DRAFT
Which product(s) are affected by this PR (if applicable)?
- [ ] amplify-cli
- [ ] amplify-ui
- [ ] amplify-studio
- [ ] amplify-hosting
- [ ] amplify-libraries
Which platform(s) are affected by this PR (if applicable)?
- [ ] JS
- [ ] iOS
- [ ] Android
- [ ] Flutter
- [ ] React Native
Please add the product(s)/platform(s) affected to the PR title
Checks
-
[ ] Does this PR conform to the styleguide?
-
[ ] Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.
-
[ ] Are any files being deleted with this PR? If so, have the needed redirects been created?
-
[ ] Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
ref: MDX:[link](https://link.com)HTML:<a href="https://link.com">link</a>
When this PR is ready to merge, please check the box below
- [ ] Ready to merge
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
