Full feature/extra support

[flying-sheep]

Python’s standard way to specify extras is mypkg[extra]. Therefore transitive extras can exist.

Hatch however only supports its own features key, not the standard syntax, when determining if the dependencies changed.

E.g. after adding a dependency to the test-min extra,hatch run test:<command> should sync dependencies fo the test environment.

[optional-dependencies]
test-min = ['pytest']
test = ['mypkg[test-min]']

[tool.hatch.envs.test]
dependencies = ['my-package-name']
features = ['test']

See also #842

[juftin]

I encountered a similar issue to this in juftin/hatch-pip-compile#78

Consider the following pyproject.toml:

[project]
name = "mypkg1234"
version = "1.0.0"

[project.optional-dependencies]
api = [
    "fastapi"
]
uvicorn = [
     "mypkg1234[api]",
     "uvicorn",
]

[tool.hatch.envs.uvicorn]
features = [ "uvicorn" ]

Inside of the EnvironmentPlugin my expected value of the dependencies property would be : ["fastapi", "uvicorn"] - but instead it's actually ["mypkg1234[api]", "uvicorn"].

I believe that unraveling the transitive dependencies on dependencies_complex would resolve this issue and mine. I'll take a look at this and see if I might be of some help.

[flying-sheep]

Awesome, thank you @ofek!