Imre Kószó

`..` still gives errors: 

I did try to work around this by re-importing the entire workspace into idea and marking all local/root refs as modules. That _did_ solve the folder mark problem and did...

Hey @cursive-ide, thanks for picking this up. I chatted to @tengstrand on the clojurians slack about this, here's what I gathered: As for the first problem you mention, while a...

@furkan3ayraktar I wouldn't completely rule out Colin's concerns wrt assumption 1 - workflows differ. However, Cursive might be able to use `workspace.edn` to find polylith roots? Is that always present...

@cursive-ide is there any update on this? Could it be a possible solution to treat active `:local/root` deps, which resolve to paths within the intellij project, source paths as opposed...

> make it easy for Cursive to resolve Polylith bricks correctly @furkan3ayraktar I would prefer a solution that is not Polylith-specific and I believe Colin is on the same opinion....

Thanks @cursive-ide. To reiterate, the suggestion `treat paths of :local/root deps that resolve to within the intellij project` is not polylith-specific. I created another repro repo to demonstrate what I...

@furkan3ayraktar thanks for reviewing this. I would caution against the extra test-paths support however. That is something tools.deps itself doesn't do, and the current issue stems from the fact that...

@cursive-ide I created yet another repro case. It still isn't polylith but somewhat closer to it. Subprojects don't reference each other on a `deps.edn` level, only in code. All subprojects...

This is still open in 1.12.4-2022.2 as discussed with @cursive-ide in a [slack thread](https://clojurians.slack.com/archives/C0744GXCJ/p1659196554317359). There are similar macros out in the wild, https://github.com/cgrand/macrovich is an example. Some devs might prefer...