Fork me on GitHub
#announcements
<
2020-04-28
>
narkisr11:04:31

Hi fellow Clojurians just wanted to share a short post I wrote about how I use Clara rules for flow automation http://narkisr.com/posts/27-04-2020-clara-flow/ in https://github.com/re-ops/re-core

16
šŸ“ 1
holyjak15:04:22

Better place is #news-and-articles

šŸ‘ 1
narkisr08:04:56

Cool had no idea that channel existed ill use that one next time, thanks for heads up

Helins16:04:58

A new Clojure/script library for automatically serializing functions and impossible things like infinite sequences : https://github.com/dvlopt/fdat.cljc The idea is pretty simple, but it was really tricky to reach a solution that would work with different serializers (currently Nippy and Transit), both in Clojure and Clojurescript. For my work, this is extremely useful. Way more convenient than, for instance, serializing vectors like [:my-fn-or-event 1 2 :argument] that we have to curate and handle ourselves. Here, we just use functions as functions, and given a minimum of intrusion, those functions are automatically serializable. Please, let me know if the README is clear enough and if you find the whole idea interesting ;)

šŸŽ‰ 3
Eccentric J17:04:06

Can you add an example of the serialized output to the README?

šŸ‘ 1
jaihindhreddy18:04:59

In the first code snippet in this section: https://github.com/dvlopt/fdat.cljc#automatically-annotating-imetas-using-the--macro Is 'user/range-range a typo for 'user/random-range?

jaihindhreddy18:04:49

Also, typos s/explicitely/explicitly/ s/destructing/destructuring/ s/counterintuive/counterintuitive/ s/medata/metadata/

Helins19:04:30

@U883WCP5Z Thanks, too much typing for the day! @U8WFYMFRU, the output is whatever the chosen serializer uses. If you use Nippy with the Nippy plugin, you will get a byte-array. I don't know if that helps?

Eccentric J19:04:58

Oh! I was under the impression that it returns strings but I guess Iā€™m not familiar enough with the problem space.

Helins19:04:36

That's the thing, the core API does not do the serialization itself, it provides utilities for existing ones. It is a bit hard to explain if you don't use that sort of things (nippy or transit).

oliy20:04:09

Martian, the http abstraction library 0.1.12 release https://github.com/oliyh/martian This releaseĀ adds supportĀ for: ā€¢ Path parametersĀ https://github.com/oliyh/martian/pull/75Ā (thanksĀ https://github.com/RafaeLeal) ā€¢ Route definition specĀ https://github.com/oliyh/martian/pull/78Ā (turn on spec instrumentation to use it) ā€¢ clj-http-lite moduleĀ https://github.com/oliyh/martian/pull/81Ā (thanksĀ https://github.com/deas) This releaseĀ improves: ā€¢ Handling of additionalPropertiesĀ https://github.com/oliyh/martian/pull/76Ā (thanksĀ https://github.com/RafaeLeal) ā€¢ Handling of open mapsĀ https://github.com/oliyh/martian/pull/77Ā (thanksĀ https://github.com/RafaeLeal) ā€¢ Remove implicitĀ `martian-httpkit`Ā dependency fromĀ `martian-test`Ā https://github.com/oliyh/martian/pull/82Ā (thanksĀ https://github.com/davidjameshumphreys)

šŸ‘€ 4
aw_yeah 1