Fork me on GitHub
#polylith
<
2023-04-10
>
Jungin Kwon02:04:27

How do you feel about creating development folders for each project? Like this.

projects/
	{project-1}/
		development/ <--- here!
			{project-1}/
				src/
					user.clj
		test/
		deps.edn
I'm using Calva and in my case, I don't have to develop multiple projects in one REPL. Is this the correct usage?

seancorfield03:04:14

If you only want a REPL for one project, why not start it in the project folder? Why do you need another development folder per project? I guess I don't understand your use case...

seancorfield03:04:40

You should be able to jack-in via the project deps.edn file and select the :test alias...

Jungin Kwon03:04:02

Exactly! Starting in the project folder is what I want.

Jungin Kwon03:04:05

I just wanted to make sure it wasn't weird to add a development folder to the project.

pez08:04:54

I think @U04V70XH6 might have missed a plural s there, or rather it got ambiguous about which project. If so, the questions is why you don’t start the repl at the Polylith root? Is there a point in denying your repl access to everything?

tengstrand10:04:51

Yes, I think the standard way of working with your code from the development project should be enough, and the recommended way. If you have several components implementing the same interface, then you can use profiles to solve that. I’m not really sure what your use case is here @U027B5AEPCG?

Jungin Kwon05:04:42

Sorry for late reply. This is because each project uses its integrant. Then cannot be running at the same time.

Jungin Kwon05:04:16

And there is also the advantage of being able to use the test alias right away by jack-in in the project. I don't want to copy the extra-deps in the project's test alias to the root as well.

seancorfield15:04:54

We use Component at work and can have every server process running in the same REPL. In some of our tests, we run multiple instances of Components at the same time. I didn't realize Integrant restricted you like that?

😿 2