nice-florist-5595807/21/2022, 6:07 PM
. With pants*d* these changes are not detected of course (and I guess this demonstrates
or other builtin functions are no exception to the rationale for prohibiting imports in BUILD files as they can "easily break Pant's cacheing mechanisms"). I haven't messed with macros yet, but would these two use cases be solved by them? Or is there a way to manually invalidate a file pattern when invoking pants w/ pantsd enabled?
) so whenever one is added, the
targets don't need to all be updated.