polylith 2021-07-25 | Slack Archive

tengstrand10:07:36

ANNOUNCEMENT. Hi everyone! I need some help from you who run the poly tool from the master branch (which should be most of you, except for @seancorfield). Follow the instruction https://github.com/polyfy/polylith/blob/issue-66/doc/migrate.md and if you do the migration in a separate branch, it should even be okay to commit and push the code after the migration. The code in the issue-66 branch will soon become the v0.2.0-alpha10 version. If everything seems to work, I will merge the issue-66branch to master. It’s getting closer, but I need an okay from you first! 🙂

👍 6

🎉 3

tengstrand10:07:15

Please reply in this thread and report how the migration went.

furkan3ayraktar14:07:34

#Also sent to the channel

I and @tengstrand have migrated my Scrintal codebase to the latest version of the Polylith using f7e8cd7fe83f6d2fdfdedda35fed5806ac418964 in the issue-66 branch. The only thing I needed to do was moving a couple of dependencies after the poly migrate command did its job. Otherwise, everything went smoothly! To give an idea of how big the workspace was, I’m attaching some screenshots below.

😮 5

👍 2

seancorfield21:07:40

In the migrate doc, you have: > :project-to-alias is replaced by :projects where each project stores a map with the name as its key and a map as value with the key :name ... Shouldn't that be :alias, not :name?

tengstrand03:07:19

Yes, that should be :alias. Nice catch. Will update.

furkan3ayraktar14:07:34

replied to a thread:ANNOUNCEMENT. Hi everyone! I need some help from you who run the `poly` tool from the `master` branch (which should be most of you, except for @seancorfield). Follow the instruction https://github.com/polyfy/polylith/blob/issue-66/doc/migrate.md and if you do the migration in a separate branch, it should even be okay to commit and push the code after the migration. The code in the `issue-66` branch will soon become the `v0.2.0-alpha10` version. If everything seems to work, I will merge the `issue-66`branch to `master`. It’s getting closer, but I need an okay from you first! :slightly_smiling_face:

I and @tengstrand have migrated my Scrintal codebase to the latest version of the Polylith using f7e8cd7fe83f6d2fdfdedda35fed5806ac418964 in the issue-66 branch. The only thing I needed to do was moving a couple of dependencies after the poly migrate command did its job. Otherwise, everything went smoothly! To give an idea of how big the workspace was, I’m attaching some screenshots below.

😮 5

👍 2

2021-07-25

Channels