You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run gazelle - I have to deal (manually fix) with a bunch of cyclic dependencies. Each time I refactor, I run gazelle to regenerate the build files. Even if changes are isolated to a sub-directory, I have to run gazelle on entire workspace. It appears on each run, we map package to build target -- so if we try running gazelle only on a sub-directory, it does not resolve imports from other directories.
Is there a way to create a cache of such mapping and update it with new runs?
The text was updated successfully, but these errors were encountered:
Unfortunately not easily - see bazelbuild/bazel-gazelle#1181 for some discussion on this topic. I definitely agree that this would be a useful thing to have!
We have large build targets (one for each top level directory) in https://github.com/harness/harness-core.
When I run gazelle - I have to deal (manually fix) with a bunch of cyclic dependencies. Each time I refactor, I run gazelle to regenerate the build files. Even if changes are isolated to a sub-directory, I have to run gazelle on entire workspace. It appears on each run, we map package to build target -- so if we try running gazelle only on a sub-directory, it does not resolve imports from other directories.
Is there a way to create a cache of such mapping and update it with new runs?
The text was updated successfully, but these errors were encountered: