This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-17
Channels
- # beginners (42)
- # cider (1)
- # cljs-dev (20)
- # clojure (73)
- # clojure-italy (8)
- # clojure-nl (53)
- # clojure-spec (11)
- # clojure-uk (88)
- # clojurescript (170)
- # clojutre (6)
- # core-async (26)
- # css (2)
- # cursive (13)
- # data-science (10)
- # datomic (15)
- # editors (3)
- # figwheel (28)
- # figwheel-main (67)
- # fulcro (57)
- # graphql (2)
- # immutant (2)
- # jobs (1)
- # jvm (4)
- # lein-figwheel (3)
- # leiningen (1)
- # off-topic (5)
- # pedestal (28)
- # re-frame (86)
- # reagent (18)
- # reitit (8)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (78)
- # spacemacs (10)
- # specter (12)
- # tools-deps (32)
- # vim (3)
@hiredman thanks again. I see what you mean. I’ve changed it so that each step thru the sequence functions at the beginning returns a fully realized section that is placed on the chan.
Guys when you are (manually)testing your graphql api-endpoints, are you using curl or something like Insomnia?
@jarvinenemil we use a small util we wrote internally https://github.com/duedil-ltd/graphql-integration-testing
Question: I am using a library called Nippy
from taoensso
. I am serializing this object but I am also using this library called Cheshire
that encodes our map into JSON. The problem I run into is that when cheshire
tries to encode a nested map that has been serialized, it breaks. It complains Cannot JSON encode object of class: class [B: [B@3384e3c0
I mean the problem makes sense so its not that I expected anything I just didn't think this far ahead until now that I am running into the issue
for a serialization library that is easy to extend to specific types and allows a json formatted target, there's cognitect/transit btw
it's easy to add custom serializers / deserializer for any type you like with transit
it does, which is kind of what I was getting at with "what did you expect?" because depending on what you want to happen, you might be able to make it do that
maybe the most common thing to do with bytes in json is to encode it as a base64 encoded string
Thanks because I had no idea what or how to encode that byte array into a JSON suitable format
cheshire also supports a binary format called smile which is similar to json, and may support encoding bytes
sadly with cheshire the encoding options are a global config - but isn't nippy already a serialization format? what's the usecase for serializing your serialized data again?
if what you need is an efficient round-trip format that is also readable as json as an intermediate representation, transit does that, but first you might want to make sure that's really your goal
and with a global config you can make cheshire accept any class you like as well
getting stuck with Java interop I’m trying proxy and reify interface com.google.pubsub.v1.MessageReciver
there's no this arg with reify is there? that's not the issue
is reciveMessage something it gets from a concrete class it inherits from?
because proxy can handle that, reify can't
its is just the interface https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/google-cloud-clients/google-cloud-pubsub/src/main/java/com/google/cloud/pubsub/v1/MessageReceiver.java
to be clear, you specify reciveMessage above, and the class defines receiveMessage - disregard if that's trivial of course
(what you showed above can't be the real code as neither of those would have worked)