-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update custom operations documentation with supported argument examples #8260
base: main
Are you sure you want to change the base?
Conversation
values: ['ACCEPTED', 'REJECTED'] | ||
}), | ||
|
||
echo: a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit -- can we use a different operation name to differentiate it from the example used in Step 1-3 on this page?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! I will use a different name
- **Custom Types**: Define inline `customType`. | ||
- **Reference Types**: Use `a.ref()` to reference enums and custom types. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- **Custom Types**: Define inline `customType`. | |
- **Reference Types**: Use `a.ref()` to reference enums and custom types. | |
- **Custom Types**: Define inline `customType` | |
- **Reference Types**: Use `a.ref()` to reference enums and custom types |
nit, we can omit the periods in unordered lists when we are not writing complete sentences or paragraphs
Description of changes:
Updated the custom operations documentation to include examples of supported argument types. This update aligns with the recent feature addition in PR #497.
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)?
Which platform(s) are affected by this PR (if applicable)?
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://docs.amplify.aws/)
HTML:
<a href="https://docs.amplify.aws/">link</a>
When this PR is ready to merge, please check the box below
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.