polylith 2021-09-13 | Slack Archive

tengstrand04:09:00

Hi everyone! I’ve added a https://polylith.gitbook.io/polylith/architecture/bring-it-all-together page to the high-level doc, which hopefully will help people, new to Polylith, understand better how it can be used in practice. I also added a “Blog posts” section to the https://polylith.gitbook.io/polylith/conclusion/next-steps page. Enjoy!

💯 10

robert-stuttaford06:09:53

Another good slack channel bookmark 🙂

👍 2

steffan10:09:31

On the "Bring it all together" page, should "wealthy" be "healthy" instead?

tengstrand11:09:39

Updated! Thanks!

pavlosmelissinos09:09:26

In the deps.edn file of the poly tool, I can see that there's a https://github.com/polyfy/polylith/blob/ad5693b5f0a7ec7bdbab56e94c02ca7df120f1a9/deps.edn#L32-L71. Am I right to assume that the recommended way to define dev dependencies on bricks for a polylith monorepo is with local/root coordinates under extra-deps? (I am not using cursive so I'm probably not affected by the bug you mention in the comment)

tengstrand10:09:22

Yes, you can use the :local-root syntax in the root deps.edn file. When doing that, make sure you also specify the tests as paths (`:aliases > :test > :extra-paths`). This should work in most IDEs. Tor the projects under the projects directory, the :local-root statements are enough, at least if you use the built in test runner.

💣 2

pavlosmelissinos09:09:35

Right, thanks! 🙂

👍 2

ivangalbans15:09:36

> make sure you also specify the tests as paths (`:aliases > :test > :extra-paths`) @U1G0HH87L could I express the tests as extra-deps too? In Emacs/Cider it works for me without problem or is there any reason why you think it is better to keep the tests in extra-paths ?

tengstrand16:09:44

Then I guess it’s fine. It’s just that in tools.deps.alpha the tests are not included when you include code via :local/root but maybe different IDES’s do that anyway.

2021-09-13

Channels