Fork me on GitHub
#portkey
<
2018-05-11
>
viesti11:05:31

I used to think that aws-clj-sdk was a bit of NIH, but the approach seems more right to me now. Amazonica gets quite far, but there is feeling of a stronger grip in going to the APIs directly.

tatut13:05:17

Can aws-clj-sdk provide better docs and arglists than amazonica?

tatut13:05:59

I really disliked that the arguments in amazonica are like string-1 string-2 input-stream-1… difficult to say what they are

1
tatut13:05:17

although I understand the technical reason (can’t get the argnames by reflecting the client Java class)

cgrand13:05:27

1/ shapes-as-specs would show up in doc output (doc for free) 2/ I believe that @viesti is working on exploiting these fine json files https://github.com/aws/aws-sdk-ruby/blob/master/apis/lambda/2014-11-11/docs-2.json

tatut13:05:39

oh yes, I think I did some line-breaking stuff for the docs

tatut13:05:42

now I remember

tatut13:05:21

:thinking_face: are the AWS APIs implemented in Java, names like "UploadFunctionRequest$FunctionZip" seem like inner class names to me

cgrand13:05:49

Maybe but here the $ seems to denote more a field than an inner class (FunctionZip is a Blob)

viesti15:05:37

docs are extracted, and for example cider spec browsing works quite nicely

viesti15:05:15

might be even more descriptive than python/boto kwargs version

viesti15:05:41

we just need to support more carrier protocols, to have complete success :)