polylith

https://polylith.gitbook.io/ and https://github.com/polyfy/polylith
domparry 2021-05-11T17:23:02.206100Z

Our first migrated polylith app went live today. Its a rather big application. It's all in a single base, and a single project.

šŸ‘ 5
7
2021-05-12T10:04:34.209Z

What is this issue-66 branch?

steffan 2021-05-12T11:39:09.209200Z

The issue description captures the details well : https://github.com/polyfy/polylith/issues/66

steffan 2021-05-12T11:41:39.209500Z

Work on resolving issue 66 is ongoing in the issue-66 branch : https://github.com/polyfy/polylith/tree/issue-66

steffan 2021-05-12T11:45:01.210Z

Some more info on progress in the Github project : https://github.com/polyfy/polylith/projects/1

tengstrand 2021-05-12T11:45:21.210200Z

In the beginning, the tools.deps CLI tool supported relative :paths like ā€œ../../components/comp1/srcā€ but since some time ago, this produces a warning. Alex Miller opened the https://github.com/polyfy/polylith/issues/66 and explained that this support will be dropped in the future. Iā€™ve been working with solving this problem since then in the https://github.com/polyfy/polylith/tree/issue-66. So far Iā€™ve recommended people to use the master branch, and the reason is that I will introduce a couple of breaking changes in the issue-66 branch, which you will have to manage manually, like small changes to workspace.edn . The internals format returned by the ws command will also change. Some people, like @seancorfield are already using the issue-66 branch. The issue-66 branch uses :deps and :extra-deps to specify dependencies to bricks (components and bases) but also supports :paths and :extra-paths as before. You also get rid of the warnings from the tools.deps CLI tool. So if you want to be on ā€œbeading edgeā€ then :issue-66 is for you (if you are also okay with using the tools-deps CLI tool, e.g. ā€œclj -M:poly infoā€, because the poly tool is based on the main branch).

2021-05-12T12:03:21.210500Z

Iā€™m in the process of migrating a bunch of repos to a single Polylith so those are important information and insights thanks, I think Iā€™m gonna stick to master for now.

šŸ‘ 2
domparry 2021-05-11T17:23:16.206200Z

Now to start the decomposition process.

domparry 2021-05-11T17:24:22.206300Z

And to migrate the rest of the services into the workspace.

tengstrand 2021-05-11T18:29:04.206700Z

Okay, cool! Do you use the master branch or the issue-66 branch?

tengstrand 2021-05-11T18:31:11.206900Z

How many lines of code is the workspace? (you can type ā€˜poly info :locā€™ to view that).

2021-05-11T19:23:59.207400Z

we're using the master branch, poly info :loc says 19,165 loc

tengstrand 2021-05-11T20:12:01.207800Z

Ok, cool.