Conflicting "require" intent

[thheller]

Cursive tries to suggest a require/import alias that is already defined.

In my app I have some older coded that uses (:require [clj-http.client :as http]) and some code that uses (:require [org.httpkit.client :as http]). Both libraries provide a http/get function, although the httpkit version does it through a macro. Cursive does not seem able to resolve this and tries to suggest requiring clj-http.client all the time which gets in the way of normal editing. Not sure why Cursive is not able to resolve the httpkit version but it should not suggest a conflicting require as I end up with

(ns something
  (:require [org.httpkit.client :as http]
            [clj-http.client :as http]))

[cursive-ghost]

Hmm, that's annoying. There's functionality in there to exclude packages from the auto-import functionality but the equivalent for namespaces doesn't exist yet - the import part comes from IntelliJ since it's used for Java.