You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is that link knowable/constructable from the underlying data that drives this library's description of available operations? If so, that could be a helpful addition to cognitect.aws.client.api/doc , a la:
(require '[cognitect.aws.client.api :as aws])
(defs3 (aws/client {:api:s3}))
(aws/doc s3 :PutObject)
;=> -------------------------;=> PutObject;=> ;=> Adds an object to a bucket.;=> https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html;=> ;=> -------------------------;=> Request;=> ...
The text was updated successfully, but these errors were encountered:
Actually, the service data for s3 does include documentationUrls for its operations, but that's the only one. I've updated the api/doc-str (used by api/doc) to present the documentationUrl when available.
I've also added an issue to the aws-sdk-js project requesting documentationUrl be added for every op on every service. As that is addressed, we'll see the docs appear in aws-api for other services.
Description
AWS has usually-helpful API documentation outlining the purpose of API docs, and the meaning of (and caveats for) request/response values - for example, https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html
Is that link knowable/constructable from the underlying data that drives this library's description of available operations? If so, that could be a helpful addition to
cognitect.aws.client.api/doc
, a la:The text was updated successfully, but these errors were encountered: