Re: Trouble understanding clojure.spec.alpha/problems :path :via :in

f Expound, but I > will soon be providing a cleaner set of functions that allows clients to do > more with the :clojure.spec.alpha/problems, including one that will provide > a `in` path that works around these issues (in most common cases). > > Ben > > On Wednesday, July 12, 2017

Trouble understanding clojure.spec.alpha/problems :path :via :in

Hi everyone, I started exploring the clojure.spec "better user errors" thing and I'm having some trouble matching clojure.spec.alpha/problems inside :clojure.spec.alpha/value in explain-data. I'm trying to understand if there is currently a way of using problem to directly find the part of the

Re: [ANN] inspectable 0.1.0 Improve your repl experience when usingclojure.spec

cent talk about REPL-Driven > Development and pluggable inspectors etc? > > > > Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN > An Architect's View -- http://corfield.org/ > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood >

[ANN] inspectable 0.1.0 Improve your repl experience when using clojure.spec

What? A couple of tools for Clojure to help you work with clojure.spec in the repl with the spirit of improving error messages. Where? [inspectable "0.1.0"] https://github.com/jpmonettas/inspectable Summary? Inspectable 0.1.0 contains two tools - borwse-spec : A GUI spec registry browser. -

Re: [ANN] expound 0.1.2

That was a great description Ben! So agree with everything there. One important difference is that inspectable doesn't support clojurescript yet, since it's using a swing interface to draw the ui I'm trying to figure out the best way to support it. My idea on inspectable is putting there a

Re: [core.spec] Stricter map validations?

I added some stuff on https://gist.github.com/stuarthalloway/f4c4297d344651c99827769e1c3d34e9 that makes your example work I think. We can

Re: Two Senior Clojure developers based in Moscow looking for the interesting challenges and possibility for remote work

Hi Sergey, Can you send your CV to tal...@district0x.io? We are looking for remote Clojure developers. Also you can apply here https://remoteok.io/remote-jobs/66945-remote-clojurescript-developer-district0x Regards, Juan El jueves, 2 de agosto de 2018, 12:56:19 (UTC-3), Sergey Tashbayev

[ANN] clj-tree-layout

Hi everybody! Maybe someone else find this useful. clj-tree-layout A library for laying out tree nodes in 2D space for Clojure and ClojureScript. Since in Clojure we are surrounded by trees (deps, specs, namespaces, sexp, execution flow, etc) I

[ANN] magic-sheet 0.1.0

Make all those Clojure[Script] repeating repl commands one keystroke away. Connect to any repl server (lein repl, fighwheel nrepl so far), define some commands and run them with a keystroke. Lots of times when developing or dev testing Clojure[Script] applications I find myself at the repl

Re: [ANN] clindex 0.2.3 - a Clojure[Script] source file indexer

x/scanner.clj#L278 > > Is that something that's a result of my setup (using leiningen)? > > > > On Monday, 4 November 2019 13:37:49 UTC+1, Juan Monetta wrote: >> >> https://github.com/jpmonettas/clindex >> >> Clindex is a general and extensible Cloju

[ANN] clindex 0.2.3 - a Clojure[Script] source file indexer

dev tools so they don't have to deal with the complexities of understanding Clojure code by reading the filesystem. Instead as an api for talking about your code it gives you a datascript db full of facts you can use together with d/q, d/pull, d/entity, etc. -- Juan Monetta -- You received

Re: [ANN] clindex 0.2.3 - a Clojure[Script] source file indexer

I guess this is a completely valid content. > > > On Tuesday, 5 November 2019 12:28:08 UTC+1, Juan Monetta wrote: >> >> Thanks Juraj! >> >> If I have to guess it is probably including a different version of >> tools.namespace. >> I forked tools.namespa

Re: [ANN] clindex 0.2.3 - a Clojure[Script] source file indexer

re-experiments/blob/master/src/clojure_experiments/books/sicp/ch1_abstractions_procedures/exercise.clj#L191 >> Is that a known limitation? I can see that's unusual in a production >> codebase but I guess this is a completely valid content. >> >> >> On Tuesday, 5 Novembe

Re: How to safely print structures that may contain infinite lazy seqs?

Hi Austin, Since there is no way to know the length of a lazy-seq without realizing it, I think your only choice is to set a limit on it by binding *print-length* if you are not sure about the sequence. Other thing you can try is bounded-count like this : (defn looks-finite? [xs] (let

ANN: FlowStorm 2.0, a Clojure debugger

I'm happy to share the latest version of FlowStorm debugger. To see a small tutorial and a demo of it being use to analyze the ClojureScript compiler check https://www.youtube.com/watch?v=YnpQMrkj4v8 Version 2.0 is a complete rewrite of the original FlowStorm debugger with a bunch of