Clojurians Log v2

First successful request made with the query protocol 😄

hello friends, So I’ve been working today on query protocol and requests (that I tried) are workgin

However there are two bugs: - I had to delete 0 arity function (I know how to solve this misconception but did not had the time)

- Error while generating 2 specs cloudformation & sns`

If you have some time @viesti (I know Christophe is on holidays), it would be awesome if you could test

it’s on the low-conform branch

here are the apis

#{"sdb" "sns" "elasticbeanstalk" "importexport" "email" "cloudsearch"
  "monitoring" "sts" "elasticloadbalancing" "elasticache" "redshift"
  "sqs" "elasticloadbalancingv2" "iam" "autoscaling" "rds"
  "cloudformation"}

might have a chance to look at it in the evening

was on holiday this week, next week at work and then 3 weeks on holiday

user=> (doc sns/list-topics)
-------------------------
portkey.aws.sns/list-topics
([] [list-topics-input])
  Returns a list of the requester's topics. Each call returns a limited list of
topics, up to 100. If there are more topics, a NextToken is also returned. Use
the NextToken parameter in a new ListTopics call to get further results.
Spec
  args: (? :portkey.aws.sns/list-topics-input)
  ret: (and :portkey.aws.sns/list-topics-response)
nil
user=> (sns/list-topics)
{:request-time 393, :repeatable? false, :protocol-version {:name "HTTP", :major 1, :minor 1}, :streaming? true, :chunked? false, :reason-phrase "OK", :headers {"x-amzn-RequestId" "f956b341-dab3-5905-8ee2-e0fde751a180", "Content-Type" "text/xml", "Content-Length" "404", "Date" "Sun, 08 Jul 2018 16:28:18 GMT", "Connection" "close"}, :orig-content-encoding nil, :status 200, :length 404, :body "&lt;ListTopicsResponse xmlns=\"<http://sns.amazonaws.com/doc/2010-03-31/\>"&gt;\n  &lt;ListTopicsResult&gt;\n    &lt;Topics&gt;\n      &lt;member&gt;\n        &lt;TopicArn&gt;arn:aws:sns:eu-west-1:262355063596:datomic-tiuhti-Compute-CS1UK5K6HXWP-dlq&lt;/TopicArn&gt;\n      &lt;/member&gt;\n    &lt;/Topics&gt;\n  &lt;/ListTopicsResult&gt;\n  &lt;ResponseMetadata&gt;\n    &lt;RequestId&gt;f956b341-dab3-5905-8ee2-e0fde751a180&lt;/RequestId&gt;\n  &lt;/ResponseMetadata&gt;\n&lt;/ListTopicsResponse&gt;\n", :trace-redirects []}

Yes cool

The post request are more hard to do but I checked every type

hum, is the ec2 protocol a variation of query?

and the body needs xml->edn

but huge progress 🙂

@viesti uploaded a file: https://clojurians.slack.com/files/U06QSF3BK/FBMSBEEEB/cider-browse-spec.gif

You have to share your emacs config

soo awesome

I don’t dare 😄

I am a 4 months emacs veteran ^^

But I love it

but luckily cider comes with spec browser that fits really nicely to the generated specs

I did not know that

and ec2 is a protocol in itself

also, I think it would be really helpful to write specs generator and put some in the doc

looking for documentation is painful today

did dare, might be dated and full of useless things, probably better to do package-list-packages and install cider 🙂 https://github.com/viesti/dotfiles/blob/master/.emacs

for amazon, have to first cut trail through marketing material, then to the technical docs

specs could use docstring support

I think Christophe had a stab at that direction

yes but we could write generators so that exercice works fully

yes, like for the SNS ARN in the above gif

for example

yup

sadly the json specs don’t go to that detail

it should be doable

but it’s not a priority

so ec2 and rest-xml should be almost the same

and then json has been done, I have to review it and put ther ser/req protocol

we could at least delete 100/200 lines of code

there are a lot of duplicates but it’s fine for now

also I think it would be best to split code into more files

yeah, have to figure out suitable blobs of dependencies

my opinion : 1) finish all protocol 2) then deser/resp 3) refactor / delete code 4) split into namespaces 5) cljs stuff 6) better docs 7) communicate

(interpose communicate-progress-or-ideas) also :)

lol, absolutely

I am not the very best for this

problem of all humanity, to transfer ideas of building things :)

but thinking out loud helps even