What would be the workflow for a multi-frontends project?

[goffi-contrib]

Hello,

I'm currently migrating my project from setup.py legacy files to Hatch, thank you for the work done there, the tool is nice.

However I'm not sure how to handle my specific case: I'm working on a project with a backend and several frontends. Frontends are in their own separated projects.

During dev, backend and frontends are often evolving in parallel, before I push them to the Mercurial repos.

In my old setup, I was handling that by pip install -e . in the backend and all frontends in the same venv.

With hatch however, the tool is built to have isolated environments. I've thought about overriding dependencies in tool.hatch.envs.dev to use local dependencies, but I would have to duplicate the whole project dependencies, this is cumbersome and hard to maintain.

Using extra_dependencies is not possible, because it would conflict with project dependencies (and I need to keep the backend dependency there for frontends, to be sure that it's installed correctly with pip install).

An other option would be to specify a common venv by using the path option in [tool.hatch.envs.dev], but again I would have a conflict in frontend with the backend dependency.

So how can I handle this kind of use case?

Thanks!

[goffi-contrib]

The currently best option I've found is to have a dev environment with the path set to a common venv in both projects. If I install the backend first, it's working. Not sure if it's the way to go though.

edit: in fact it's not working, the frontend is not installed correctly for whatever reason. For now the only way I've found is to manually to pip -e . in backend directory from my frontend venv. I guess #588 would be of great help here.