Skip to content
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 externalDocumentation to a named map #363

Merged
merged 1 commit into from
Apr 8, 2020
Merged

Conversation

kstich
Copy link
Contributor

@kstich kstich commented Apr 7, 2020

This commit updates the @externalDocumentation trait to be a map of
named urls instead of a single url. This provides more context for
the given links and enables the ability to have multiple links per
trait application.

An update to the OpenApi conversion has been made to utilize this
when populating "externalDocs" fields. A configurable, priority
ordered list of url names is available through
"openapi.externalDocs"; it defaults to "Homepage", "Api
Reference", "User Guide", "Developer Guide", "Reference", and
"Guide". This list is compared case insensitively. This also
fixes an issue where "externalDocs" fields could be generated as
strings instead of the properly formatted external documentation
object in the resulting OpenApi document.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@kstich kstich requested a review from mtdowling April 7, 2020 22:08
@@ -8,7 +8,9 @@
"selector": "service"
},
"smithy.api#documentation": "Specifies the source of the caller identifier that will be used to throttle API methods that require a key.",
"smithy.api#externalDocumentation": "https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-swagger-extensions-api-key-source.html",
"smithy.api#externalDocumentation": {
"User Guide": "https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-swagger-extensions-api-key-source.html"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we call this "Developer Guide" so that it matches the nomenclature of the referenced docs?

docs/source/guides/converting-to-openapi.rst Outdated Show resolved Hide resolved
docs/source/guides/converting-to-openapi.rst Outdated Show resolved Hide resolved
@kstich kstich force-pushed the external_doc_map branch from 0d78257 to e0cbe96 Compare April 8, 2020 19:33
@kstich kstich requested a review from mtdowling April 8, 2020 19:34
This commit updates the @externalDocumentation trait to be a map of
named urls instead of a single url. This provides more context for
the given links and enables the ability to have multiple links per
trait application.

An update to the OpenApi conversion has been made to utilize this
when populating "externalDocs" fields. A configurable, priority
ordered list of url names is available through
`"openapi.externalDocs"`; it defaults to "Homepage", "Api
Reference", "User Guide", "Developer Guide", "Reference", and
"Guide". This list is compared case insensitively. This also
fixes an issue where "externalDocs" fields could be generated as
strings instead of the properly formatted external documentation
object in the resulting OpenApi document.
@kstich kstich force-pushed the external_doc_map branch from e0cbe96 to 86bdb97 Compare April 8, 2020 19:38
@kstich kstich merged commit 98eab25 into 0.10 Apr 8, 2020
@kstich kstich deleted the external_doc_map branch April 8, 2020 20:01
@kstich kstich mentioned this pull request Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants