Open ghorn opened 5 years ago
Any estimates on how hard this would be? This is blocking the use of protobufs for us.
cc @flokli @guibou
@ghorn for now you can just add Proto.Samples.Protobufs.HelloWorld.HelloWorld
in the ignore list of your custom haddock.
GitHub autoclosed this due to the description in #1108, but it's not yet fixed, so reopening.
This seems to still be an issue.
$ bazel test //tests/haddock_protobuf:all
...
INFO: From HaskellHaddock //tests/haddock_protobuf:hello_world_haskell:
Warning: HelloWorld: could not find link destinations for:
- Proto.Tests.HaddockProtobuf.HelloWorld.Person
...
And the generated haddocs don't include the protobuf symbols.
rules_haskell rev dabf7afd9d5dc622d187a71169e2bb6b54ca3a8f bazel version 0.28
I have a build file something like:
It's a bazel
proto_library
which ahaskell_proto_library
depends on, and a normalhaskell_library
which imports thehaskell_proto_library
.When I try to generate haddocks depending only on the
haskell_library
I get a warning that the proto is not in scope:When I try to generate haddocks depending also on the
haskell_proto_library
, I get arules_haskell
error something like:I assume that this is unsupported functionality.
This is important to us adopting
haskell_proto_library
because we hacked haddock to error on warnings.