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
{{ message }}
This repository has been archived by the owner on Sep 15, 2021. It is now read-only.
If, in a transitive bzl_library dependency, one of the sources is generated, the input file to stardoc instead of living under the workspace lives under bazel-out instead of relative to the execution root. Stardoc thus has no idea where to find it.
Correct -- the use case is a team which exposes a bzl_library which explicitly stubs out their "real" rules. This team's users write macros pointing to the team's rules. When these users want to test their own macros, the team encourages their users to depend on the "stub" bzl_library instead of the "real" implementation.
It's a little backwards, but since bzl_library does technically allow generated files, we should have Stardoc handle this case nicely.
bazel-io
pushed a commit
to bazelbuild/bazel
that referenced
this issue
Feb 11, 2019
If, in a transitive
bzl_library
dependency, one of the sources is generated, the input file to stardoc instead of living under the workspace lives under bazel-out instead of relative to the execution root. Stardoc thus has no idea where to find it.For example, a proper input file path looks like:
But a generated input file path looks like:
My plan here is:
Modify Stardoc binary to take a new optional flag, "--dep_roots" each entry represents a root path directory to evaluate dependencies. To fix the example in Commit 4b71d2e1bc3afa0ce0a5b6e68dac3c559654d975 of Bazel enforce workspace name which breaks skydoc #7, we would pass
--dep_roots=bazel-out/k8-opt/bin
Stardoc will thus, when looking for a bzl file across a transitive dependency, try:
Modify the stardoc Starlark rule to include values of
--dep_roots
to the invocation of the Stardoc binary. These arguments will be added with:The text was updated successfully, but these errors were encountered: