Automatically created test namespace is wrong when nested source dir #311
Comments
|
Hmm, this definitely not in P.S. I also dislike the usage of |
|
The broken function is
|
expez
added a commit
to expez/clojure-mode
that referenced
this issue
Jul 29, 2015
…c/cljc
When the source path is src/{clj,cljc,cljs} instead of just src/
clojure-expected ns would create namespaces like clj.my-project.my-ns
whereas what's wanted is my-project.my-ns.
Reading boot.clj or project.clj to find out the user's src dirs is out
of scope for clojure-mode, so we use the simply heuristic that no
namespace should start with clj, cljc or cljs because these are the
idiomatic source directories in multi-source projects.
When improving clojure-expected-ns I extracted out two utilities,
clojure-project-dir and clojure-project-relative-path. These
utilities already exist in clj-refactor so I opted to make them public
rather than private, as they are generally useful.
expez
added a commit
to expez/clojure-mode
that referenced
this issue
Jul 29, 2015
…c/cljc
When the source path is src/{clj,cljc,cljs} instead of just src/
clojure-expected ns would create namespaces like clj.my-project.my-ns
whereas what's wanted is my-project.my-ns.
Reading boot.clj or project.clj to find out the user's src dirs is out
of scope for clojure-mode, so we use the simply heuristic that no
namespace should start with clj, cljc or cljs because these are the
idiomatic source directories in multi-source projects.
When improving clojure-expected-ns I extracted out two utilities,
clojure-project-dir and clojure-project-relative-path. These
utilities already exist in clj-refactor so I opted to make them public
rather than private, as they are generally useful.
expez
added a commit
to expez/clojure-mode
that referenced
this issue
Jul 29, 2015
…c/cljc
When the source path is src/{clj,cljc,cljs} instead of just src/
clojure-expected ns would create namespaces like clj.my-project.my-ns
whereas what's wanted is my-project.my-ns.
Reading boot.clj or project.clj to find out the user's src dirs is out
of scope for clojure-mode, so we use the simply heuristic that no
namespace should start with clj, cljc or cljs because these are the
idiomatic source directories in multi-source projects.
When improving clojure-expected-ns I extracted out two utilities,
clojure-project-dir and clojure-project-relative-path. These
utilities already exist in clj-refactor so I opted to make them public
rather than private, as they are generally useful.
expez
added a commit
to expez/clojure-mode
that referenced
this issue
Jul 29, 2015
…c/cljc
When the source path is src/clj{,c,s,x} instead of just src/
clojure-expected ns would create namespaces like clj.my-project.my-ns
whereas what's wanted is my-project.my-ns.
Reading boot.clj or project.clj to find out the user's src dirs is out
of scope for clojure-mode, so we use the simply heuristic that no
namespace should start with clj, cljc or cljs because these are the
idiomatic source directories in multi-source projects.
When improving clojure-expected-ns I extracted out two utilities,
clojure-project-dir and clojure-project-relative-path. These
utilities already exist in clj-refactor so I opted to make them public
rather than private, as they are generally useful.
expez
added a commit
to expez/clojure-mode
that referenced
this issue
Jul 29, 2015
…c/cljc
When the source path is src/clj{,c,s,x} instead of just src/
clojure-expected ns would create namespaces like clj.my-project.my-ns
whereas what's wanted is my-project.my-ns.
Reading boot.clj or project.clj to find out the user's src dirs is out
of scope for clojure-mode, so we use the simply heuristic that no
namespace should start with clj, cljc or cljs because these are the
idiomatic source directories in multi-source projects.
When improving clojure-expected-ns I extracted out two utilities,
clojure-project-dir and clojure-project-relative-path. These
utilities already exist in clj-refactor so I opted to make them public
rather than private, as they are generally useful.
expez
added a commit
to expez/clojure-mode
that referenced
this issue
Jul 29, 2015
…c/cljc
When the source path is src/clj{,c,s,x} instead of just src/
clojure-expected ns would create namespaces like clj.my-project.my-ns
whereas what's wanted is my-project.my-ns.
Reading boot.clj or project.clj to find out the user's src dirs is out
of scope for clojure-mode, so we use the simply heuristic that no
namespace should start with clj, cljc or cljs because these are the
idiomatic source directories in multi-source projects.
When improving clojure-expected-ns I extracted out two utilities,
clojure-project-dir and clojure-project-relative-path. These
utilities already exist in clj-refactor so I opted to make them public
rather than private, as they are generally useful.
|
This can be closed too, was hoping github would understand multiple issues closed by same commit |
|
Thanks for the quick response guys. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Assume I have
src/cljc/a/b/c.cljc. If I navigate in dired to test/cljc/a/b and then C-x C-f new_test.cljc then a new buffer is helpfully created(ns cljc.a.b.new_test)(filed in #310). However, it also requires:(In terms of style I would suggest it is actually
[a.b.new :as sut]for consistency, but that is a personal style issue).Namespaces are setup correctly so
src/cljcis a source path andtest/cljcis a test path according to project.clj.Libraries are Clojure 1.7.0 and snapshot cider.
The text was updated successfully, but these errors were encountered: