google / google/flatbuffers

Bazel rule rewrite

Open
#8,941 3 comments 0 reactions 0 assignees View on GitHub
CI help wanted stale
Dominant language
C++
Stars
26.5k
Forks
3.7k
PR merge metrics
No merged PRs in 30d

Description

For my use case the existing flatbuffers_cc_library isn't sufficient. For example, it can't accept filegroups as source arguments. I think the best way to handle this would be to write new idiomatic Bazel rules from scratch using providers, custom rules instead of genrules, etc. To start, it would probably make sense to implement these rules in parallel to the existing rules to give people time to migrate.

I'm willing to implement this--would such a PR be accepted or would I be better off creating a separate rules_flatbuffers project? Thanks for any advice!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.