hatch:pkg:add can add a local package or a package hosted on Hatch-Registry (currently empty with the exception of the test package base).
After the rework of the Docker image , Hatchling's code base is not close anymore from the mounted directory that exposes the local packages a user might have on its host machine to Hatchling in the container: the relative path is far away and it becomes annoying to navigate to the location.
A suggestion of enhancement is simply to have an environment variable to retrieve the root path of the local packages on the environment where Hatchling is running (the container when using docker, or the machine itself when using running directly).
This should probably be built in coordination with #12 to leverage the settings in Hatchling (although this setting specifically would be read-only because it's not something we should be able to change after building the image in the case of docker)
hatch:pkg:addcan add a local package or a package hosted on Hatch-Registry (currently empty with the exception of the test package base).After the rework of the Docker image , Hatchling's code base is not close anymore from the mounted directory that exposes the local packages a user might have on its host machine to Hatchling in the container: the relative path is far away and it becomes annoying to navigate to the location.
A suggestion of enhancement is simply to have an environment variable to retrieve the root path of the local packages on the environment where Hatchling is running (the container when using docker, or the machine itself when using running directly).
This should probably be built in coordination with #12 to leverage the settings in Hatchling (although this setting specifically would be read-only because it's not something we should be able to change after building the image in the case of docker)