Can I commit my configuration for indentation and resolution as a file to my repo?

Hm…I’m getting continual reports of cylcic requires when I use the require-macros trick in a cljc file:

I get this when I try to use nREPL reload current ns, and I also get it when trying to run tests that will reload nses

strange that this doesn’t happen to me on other projects, which makes me think I’ve made a mistake somewhere, but this is not a particularly helpful error message

Is there a way to dump the (ns ...) portion of every .cljs .cljc *.clj file ?

@todo tools.namespace has facilities for 1) finding clj(s/c) files, 2) reading the ns declaration

I would assume it could be used to dump them as well.

@potetm: Good point. With regards to @tony.kay’s problem above, I'm surprised no one has written a tool that parses all *.ns , looks for loops, and offers sensible errors [ I have run into similarly annoying to debug cyclic dependency issues in the past ]

@cfleming What’s strange is all of the code compiles and runs just fine…it’s just in cursive that it is doing this.

so that makes me thing the IDE has a bug….perhaps you could try to reproduce locally: https://github.com/fulcrologic/fulcro-incubator The feature/routing-experiment branch. Using deps.edn. Trying to run tests in the IDE for https://github.com/fulcrologic/fulcro-incubator/blob/feature/routing-experiment/src/test/fulcro/incubator/dynamic_routing_test.cljc. (Using IDE action run tests in current NS in an nREPL set up with IntelliJ classpath with Clojure Deps aliases “dev, provided, test” enabled. (at commit 1e17373fca5e04a7f298789f263ff5f5f85f4beb, this has changed based on messages below) Ah, If I split the test out of a CLJC file into a CLJ and CLJS file, then I can run the tests fine.

but then, of course, I have a ton of duplicate code (the files are otherwise identical)

Ahah! I think I found it. I was using deftest from the workspaces library (which is supposed to emit a deftest)…when I switch back to normal deftest it is fine.

not sure why the IDE gives that particular error, but dropping the use of the alternate deftest fixed it.

@tony.kay Thanks for the repro case, I’ll try that later. I don’t see why that change would affect things though.