Fork me on GitHub
#portkey
<
2018-07-08
>
baptiste-from-paris13:07:21

First successful request made with the query protocol 😄

parrot 4
baptiste-from-paris15:07:25

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

baptiste-from-paris15:07:22

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)

baptiste-from-paris15:07:49

- Error while generating 2 specs cloudformation & sns`

baptiste-from-paris15:07:57

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

baptiste-from-paris15:07:04

it’s on the low-conform branch

baptiste-from-paris15:07:33

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

viesti15:07:26

might have a chance to look at it in the evening

viesti15:07:00

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

viesti16:07:38

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 "<ListTopicsResponse xmlns=\"">\n  <ListTopicsResult>\n    <Topics>\n      <member>\n        <TopicArn>arn:aws:sns:eu-west-1:262355063596:datomic-tiuhti-Compute-CS1UK5K6HXWP-dlq</TopicArn>\n      </member>\n    </Topics>\n  </ListTopicsResult>\n  <ResponseMetadata>\n    <RequestId>f956b341-dab3-5905-8ee2-e0fde751a180</RequestId>\n  </ResponseMetadata>\n</ListTopicsResponse>\n", :trace-redirects []}

baptiste-from-paris16:07:44

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

viesti16:07:14

hum, is the ec2 protocol a variation of query?

viesti16:07:03

and the body needs xml->edn

viesti16:07:15

but huge progress 🙂

baptiste-from-paris16:07:20

You have to share your emacs config

viesti16:07:29

I don’t dare 😄

viesti16:07:30

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

baptiste-from-paris16:07:37

I am a 4 months emacs veteran ^^

viesti16:07:00

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

baptiste-from-paris16:07:11

I did not know that

baptiste-from-paris16:07:24

and ec2 is a protocol in itself

baptiste-from-paris16:07:05

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

baptiste-from-paris16:07:18

looking for documentation is painful today

viesti16:07:32

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

viesti16:07:19

specs could use docstring support

viesti16:07:34

I think Christophe had a stab at that direction

baptiste-from-paris16:07:38

yes but we could write generators so that exercice works fully

viesti16:07:12

yes, like for the SNS ARN in the above gif

viesti16:07:12

sadly the json specs don’t go to that detail

baptiste-from-paris16:07:47

it should be doable

baptiste-from-paris16:07:57

but it’s not a priority

baptiste-from-paris16:07:46

so ec2 and rest-xml should be almost the same

baptiste-from-paris16:07:10

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

baptiste-from-paris16:07:21

we could at least delete 100/200 lines of code

baptiste-from-paris16:07:31

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

baptiste-from-paris16:07:54

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

viesti16:07:15

yeah, have to figure out suitable blobs of dependencies

baptiste-from-paris16:07:17

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

viesti16:07:21

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

baptiste-from-paris16:07:55

I am not the very best for this

viesti17:07:03

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

viesti18:07:30

but thinking out loud helps even