Better distinguish `# via [current project]` comment about hatch-pip-compile HOT 8 CLOSED

Easy change in the code btw 😁

-            f"{self.metadata.name}",
+            f"hatch.envs.{self.name}",

from hatch-pip-compile.

Yeah I removed the project.toml part of it because I didn't have a clean way to tell whether the config was coming via pyproject.toml or hatch.toml.

Do you happen to know if there are easy ways to discern where the config is set?

from hatch-pip-compile.

I'm guessing there isn't a way to determine that. It looks to be merged without a trace.
https://github.com/pypa/hatch/blob/d666ae7b3dacded86faa96cc0454bb1e69132dc7/backend/src/hatchling/metadata/core.py#L206

I think it's acceptable to not mention that it's pyproject.toml. But I'm mainly saying that mentioning the project name is misleading.

from hatch-pip-compile.

Could be # via Hatch 'docs' env
or maybe # via tool.hatch.envs.docs

from hatch-pip-compile.

Could be # via Hatch 'docs' env
or maybe # via tool.hatch.envs.docs

# via hatch.envs.docs sounds like a winner to me.

How do you feel about # via hatch.envs.default though?

from hatch-pip-compile.

What do you mean? # via hatch.envs.default is good, if the env is default :)

from hatch-pip-compile.

What do you mean? # via hatch.envs.default is good, if the env is default :)

I was thinking of a situation where the default env would get the # via {self.metadata.name} while non-default envs would get # via hatch.envs.{self.name}

But, I think you're right. Just staying consistent with hatch.envs.{self.name} is the most clear

from hatch-pip-compile.

🎉 This issue has been resolved in version 1.0.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

from hatch-pip-compile.