LukeMathWalker / LukeMathWalker/pavex
feat: bazel (and/or other build system) rulesets
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
Most of the time Bazel users generate a ruleset outside of the project the ruleset is for. Exceptions include a) things like GRPC that are natively maintained using Bazel, and b) developer orientated products where the user interface is one of their concerns.
Pavex seems to fall into (b) - and because you've got a big focus on the developer experience, extending that out into users of Bazel, nix, pants2, buck2 and other related build systems will likely be relevant/important.
Because pavex is doing code generation, it -is- going to interact with those systems, as sqlx does (e.g. https://github.com/launchbadge/sqlx/pull/2927 ), and anything outside OSS sphere is IME increasingly likely to use such a system.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Pavex's code-generation workflow and how it would interact with Bazel, Nix, Pants2, Buck2, or similar build systems. The issue does not name files, tests, or a single target; done would first require narrowing this broad proposal to a specific supported system and defined integration scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100