Declare a specific constant as a Dependency about packwerk HOT 3 CLOSED

Packwerk doesn't support dependencies between anything other than packages. However, packages can be very small to the point where a package contains just one file.

You could create a package that only contains ::Job.

In our work we've found that we rarely want to be this specific. Most of the time there is a chuck of behavior that a package should be allowed to depend on, and there's no reason why that behavior should be implemented in just one file.

Note that you can also create a package that contains all your job logic, and then use package privacy to only expose the one constant that you think should be reused.

from packwerk.

@exterm thanks for the reply! I figured as much but thought I'd at least reach out and see if I was missing something. I appreciate the suggestions.

from packwerk.

@exterm I think it'd still be useful to make this explicit in the readme. Or even better, show an error when running the check. The format isn't specified anywhere and there's no error if you make a typo in the component name. Or if you try to add dependencies the wrong way. I ended up in this issue because I was trying to list specific files/folders/constants as dependencies. It isn't that obvious for a first time reader

Update: Of course 5 minutes after writing I noticed that validate notifies you about that 😅. I would still place this error within check and write it in the readme though 🙂

Thanks in any case!

from packwerk.