bazel-contrib / bazel-contrib/rules_scala
Command line option for more verbose debug logging?
- Dominant language
- Starlark
- Stars
- 384
- Forks
- 292
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 46
Description
This is a bigger issue for bazel in general, but it would be nice to be able to optionally have verbose logging in custom rules.
TwitterScroogeGenerator would be a good place to have some, and the spirit of this comment https://github.com/bazelbuild/rules_scala/blob/master/scala/scala.bzl#L102
Contributor guide
Research direction
Start with the TwitterScroogeGenerator entry point and the referenced section of scala/scala.bzl around line 102. Clarify how an optional Bazel command-line setting should reach custom rules and what verbose output is required; done means the generator can emit that logging without changing default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system, cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100