This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-02
Channels
- # beginners (26)
- # bitcoin (1)
- # boot (9)
- # boot-dev (5)
- # cider (26)
- # cljs-dev (1)
- # clojure (190)
- # clojure-finland (1)
- # clojure-italy (42)
- # clojure-nl (20)
- # clojure-russia (3)
- # clojure-sanfrancisco (1)
- # clojure-serbia (1)
- # clojure-spec (50)
- # clojure-uk (16)
- # clojurescript (62)
- # core-async (4)
- # cryogen (1)
- # cursive (6)
- # datascript (1)
- # datomic (36)
- # duct (6)
- # editors (6)
- # emacs (14)
- # graphql (3)
- # leiningen (30)
- # off-topic (21)
- # om (7)
- # parinfer (13)
- # portkey (56)
- # re-frame (2)
- # reagent (2)
- # shadow-cljs (58)
- # vim (1)
- # yada (3)
oh wau, @baptiste-from-paris this means that git submodule usage is kosher? 🙂
kosher means great in that sense ? ^^
didn’t have enough energy last night to make change to sourcing from ruby sdk, I’m glad that you took the baton 🙂
seams like it, we have a way to track updates to the ruby sdk which seems to be the first one to be updated on all public sdks
but as I mentionned, 4 libs are failing some specs
and I think it’s from new lib
as @cgrand started by the most recent protocol, it’s probable that new libs will follow that protocol
same for partitions
https://github.com/portkey-cloud/aws-clj-sdk/pull/23/files#diff-b47f4b3b24369ab8e69408fc17ce241fR1
see the endpoints to nil ?
do we need java-classpath anymore ?
and jsoup
and for the latest version, I thought the job was already done but it might have been in previous release
missed that
did I commit everything ?
in commit https://github.com/dupuchba/aws-clj-sdk/commit/d99c360eb0e3c853209f615c7cdd9c6dbd31a309
I so rarely work with submodule that I screw up every time
yeah, was hesitant because of that, but didn’t figure out quicker way of getting a specific version the specs from another repo
I vaguely remember planning on having time stamps in nses and default ns would be the latest version.
should be fixed
ok, that change a lot ^^
this project is like a never ending game it’s crazy
@viesti when you have some time, if you can look at why docs are missing
I guess they where taken from the jar file...
so the ruby sdk does NOT come with a partition file
and offcourse our partition file is NOT synced with the ruby sdk
is there any way or is it a good idea to postpone this partition problem ?
missed that one
now synced, eu-west-3
a.k.a. Paris is appearing everywhere ^^
hmm, docs are im separate files, e.g. https://github.com/aws/aws-sdk-ruby/blob/master/apis/lambda/2015-03-31/docs-2.json
some reflections while working on the query
protocol
specs that we designed for the rest-json
protocol will work and conform
but query api is clearly different, little example
the locationName
entry in the rest-json
protocol does not exist
but everything goes into the query-string for the query protocol
what I am trying to say is I still trying to figure out where doing the serizalization process