There's a regression in the 0.2.20-SNAPSHOT branch -- not sure when since I only just started testing it:
Error 101: Illegal dependency on namespace clojure.extensions in seo.geo.affiliate. Use clojure.interface instead to fix the problem.
Error 101: Illegal dependency on namespace clojure.extensions in seo.geo.locale. Use clojure.interface instead to fix the problem.
Error 101: Illegal dependency on namespace web.spec in admin.handlers.membership. Use web.interface instead to fix the problem.
Error 101: Illegal dependency on namespace web.spec in admin.handlers.promo. Use web.interface instead to fix the problem.
Error 101: Illegal dependency on namespace web.spec in api.search. Use web.interface instead to fix the problem.
These are due to external libraries that share the same top-ns as our own code (`ws` in our case -- our open source libraries from Clojars). These errors do not appear in 0.2.19.Hopefully the 101 validation should work now, in 0.2.20-SNAPSHOT #23. I have also fixed the problem that the with:test-snippet config wasn't merged into per project :test config. @seancorfield
Will check it out when I'm back at work. Thanks.
Yup, this seems to have fixed the problem. Thank you!
Sounds good!
The :test key per project should also work correctly together with the :with syntax.
There are no bricks called clojure or web so these nses should not be considered part of the workspace (and they were not considered in 0.2.19).
ws.clojure.extensions and ws.web.spec are both library nses.
This is a complete blocker for us testing 0.2.20 snapshots @tengstrand FYI
Could you export your workspace, while using the latest snapshot version, and send it to me @seancorfield?
Remind me of the preferred command...?
ws out:sean.edn
Okay, wasn't sure if you wanted any options etc on that...
So you get those 101 errors when you run a plain check command?
Yes.
Ok
That is a big file...
You can DM me.
Meanwhile, there's an update to the External Test Runner (v0.5.0) for Polylith that now supports running tests in src directories and the var/include/exclude focus options from Cognitect's test runner (i.e., either a specific list of test vars to run, or whether to include or exclude tests based on metadata such as :integration or :slow or whatever you want): https://github.com/seancorfield/polylith-external-test-runner?tab=readme-ov-file#test-configuration
You can use this with Polylith 0.2.19 and earlier by passing the test configuration as an env var, or via the new-in-0.2.20 :test-configs feature.