Re: Clojure.spec, maps, restrict valid keywords, easier way?

It would be great if an editor highlighted a (possibly qualified) keyword that was used only in that particular place (given all code loaded). This wouldn't be bullet-proof, but would have highlighted mistakes like :encypted (but could still confuse :encrypted? with :encrypted, and whatnot).

Re: Clojure.spec, maps, restrict valid keywords, easier way?

The eastwood linter can also be configured to look for possibly misspelled keyword typos https://github.com/jonase/eastwood#keyword-typos On Friday, February 3, 2017 at 3:47:21 AM UTC-7, John Schmidt wrote: > > I suggest something like (defn fetch-encrypted [] (fetch-important-data > {:encrypt

It's time for Google Summer of Code 2017!

Hello, all, We now have less than a week to prepare our application for Google Summer of Code 2017 , a program where Google pays students from around the world to work on open source projects. Clojure has successfully participated 2012–2015, and we would

Re: Clojure.spec, maps, restrict valid keywords, easier way?

I suggest something like (defn fetch-encrypted [] (fetch-important-data {:encrypt true})) + unit tests On Friday, February 3, 2017 at 2:56:34 AM UTC+1, Michael Gardner wrote: > > What would be the Right Way to deal with typos like (fetch-important-data > {:encypt true}), where the :encrypt key