Christian Edward Jackson-Gruber

I'll roll a PR. We updated it to 1.0, as we just upgraded internally, so the current code should be appropriate.

while I'm here. QQ on artifact name and folder name. Folder name: `field`, `fields`, `reflective-fields` artifact: `truth-field-extension` `truth-fields-extension` `truth-reflective-fields-extension` It uses reflection, but that's an implementation detail of HOW it...

I've tentatively gone with "fields" as a folder name, and "truth-fields-extension" as an artifact name, but it's changeable. That's just the default I picked until I hear more from folks...

Cool. Pretty close. Found some un-handled edge cases which I figured I'd fix on the way. Just fixing up the readme now.

Pinging to reopen this, as it has become a blocker on doing some things with Bazel. I'll work up an internal version of the tooling, and figure out what parts...

I'll probably upstream a variant in Q4. We are using such a wrapper in our bazel rules. I'll likely also upstream a bazel rule that consumes it.

This is a long-standing issue, it seems, related to how the [rules collect plugin info](https://github.com/bazelbuild/rules_kotlin/blob/da6e9ec5982ea7179c2658cd4a4513549d4642b0/kotlin/internal/jvm/plugins.bzl#L64) - we special case java_library, and don't special case android_library. This is wrong, but it's...

Good workaround. We still need to fix this. Sorry about that.

Yeah, this one is new to us. We can look at it, but it's not (yet) a high-priority. It seems to be pulling lots of different things from git repositories,...

For now, we're not going to be prioritizing this in advance of 1.5. We should fix it, but it is on an experimental feature, so we may not get it...