Juho Teperi

Vim lisp plugins

1

[Paredit.vim](https://github.com/kovisoft/paredit) is probably quite similar to paredit.el My favorite is https://github.com/guns/vim-sexp + https://github.com/tpope/vim-sexp-mappings-for-regular-people which is probably inspired by paredit and others. But unlike paredit, it doesn't prevent writing unbalanced code,...

Single-space indentation when no arguments on same line as function name

33

We recently had discussion about this rule at work. We have two Emacs user, single Vim user and many Cursive users and all but Emacs users found this rule strange....

Semantic UI produces bad output

1

Related: https://github.com/SomMeri/less4j/issues/295 Semantic-UI calls a mixing, which produces url @import, inside `&` block. Less.js hoists this import to top-level. Less4j leaves the `import` inside block and prints a warning. Example:...

Pattern/RegExp class schema doesn't actually check if value is RegExp instance

5

``` (m/validate #?(:clj java.util.regex.Pattern, :cljs js/RegExp) #"foo") ;; :malli.core/child-error {:type :re, :properties nil, :children nil, :min 1, :max 1} ``` I'm quite sure the implementation should check if the value...

Predicate registry doesn't work with ProGuard

3

Somehow, running AOT compiled project through ProGuard breaks any predicate schemas. ``` Caused by: clojure.lang.ExceptionInfo: :malli.core/invalid-schema {:schema #object[clojure.core$boolean_QMARK_ 0x1ba77d6e "clojure.core$boolean_QMARK_@1ba77d6e"]} {:schema #object[clojure.core$boolean_QMARK_ 0x1ba77d6e "clojure.core$boolean_QMARK_@1ba77d6e"]} {:type :malli.core/invalid-schema, :message :malli.core/invalid-schema, :data {:schema...

I can't use the predicate schemas due to #556. The built-in registry doesn't have keyword schema which would work similar to `number?` predicate schema.

Add option to add default value to optional properties

5

I have a case where I need default values to be added to the maps, even though the properties are optional. Should be simple to add new condition to `optional`...

Same as `:orn`, it could be useful to name `and` clauses so it is possible to modify them with `mu/dissoc` etc.

Json decoder doesn't convert :map key strings to keywords

2

```clj (m/decode [:map [:user-id :string]] {"user-id" "foo"} mt/json-transformer) ;; => {"user-id" "foo"} (m/decode [:map-of :keyword :string] {"user-id" "foo"} mt/json-transformer) ;; => {:user-id "foo"} ``` I think the first one should...

Is this argument for key options? Does it work? Or is it for something else? At the minimum, the docstring should mention the argument and what it does. Readme doesn't...