You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I always end up unwinding once after thread-first or thread-last. It would be nice to be able to specify a minimum depth or length of the first sexp in threading.
For instance, the following sexp
(remove #(< value 0) (filter :name (map :items return)))
Expands to this
(->> return
(map :items)
(filter :name)
(remove #(< value 0)))
I'd like a way to say “the first line should be at least 1 level deep”, so it would end up like this:
(->> (map :items return)
(filter :name)
(remove #(< value 0)))
The text was updated successfully, but these errors were encountered:
As an extra bonus, it would be nice to be able to specify a maximum length in characters for the first line. So that if the return variable has a very long name, it would still get its own line.
For instance, the following sexp
(remove #(< value 0) (filter :name (map :items the.ns/of-a-long-var-name)))
Would then still expand to this
(->> the.ns/of-a-long-var-name
(map :items)
(filter :name)
(remove #(< value 0)))
I always end up unwinding once after thread-first or thread-last. It would be nice to be able to specify a minimum depth or length of the first sexp in threading.
For instance, the following sexp
Expands to this
I'd like a way to say “the first line should be at least 1 level deep”, so it would end up like this:
The text was updated successfully, but these errors were encountered: