-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(apigateway): id in schema model maps to $id #15113
Conversation
be525b3
to
b9feb09
Compare
924c117
to
ebfd5f2
Compare
47f5bb4
to
1e5169e
Compare
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.
Looks good!
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
If we specify the `id` field when defining an Api Gateway Model's schema, it gets mapped to a `$id` key, which creates an invalid model because it doesn't comply with the DRAFT-04 specification. The specification requires this field to remain named as `id`. fixes aws#14585 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
If we specify the
id
field when defining an Api Gateway Model's schema, it gets mapped to a$id
key, which creates an invalid model because it doesn't comply with the DRAFT-04 specification. The specification requires this field to remain named asid
.fixes #14585
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license