ToBeReplaced
ToBeReplaced
As a smaller request -- being able to include raw CSS strings as rules would be useful for people with existing CSS to work with. A common case would be...
What would you recommend writing, and how is it unique to Clojure? As an example, If "ensuring input is a positive number" means "you promise to never give me a...
It depends. Make the function arguments self-documenting for the caller. If the argument is best understood as a `viewer`, the arglists should show that. I would use: ``` clojure ;;;...
What is the precedent? Do you just mean that it is most common? If so, I don't think that we should be talking about preserving the most common approach just...
I would argue that `(string :refer [join] :as string)` is more readable than `[string :refer [join] :as string]` because it is clearly a form in its own right. Otherwise, `[:refer...
That's interesting. Playing the counterpoint, would we be comfortable with: ``` clojure (ns examples.ns [:refer-clojure :exclude [next replace remove]] [:require [clojure [string :as string :refer [capitalize]] [set :as set]]]) ```...
I disagree wholeheartedly on most accounts, but I've made my claims so no need to reiterate. That said, would you advocate for a change in style from `(clojure [string :as...
@Gonzih: I meant the current recommendation in the style guide. You are right, `(:require (clojure [string :as string] set))` is rare in favor of `(:require [clojure.string :as string] [clojure.set])`. That...
I like the idea, though it would be particularly tricky for editors since there is no way to distinguish between "this is a list of independent elements" and "this is...
The way I solved this in [lettercase](https://github.com/ToBeReplaced/lettercase) was to optionally allow the user to pass in their own separator regex. In your case, it would be `(lower-underscore :s3-key #"-")`. camel-snake-kebab...