salesforce / salesforce/rules_spring
Rebuild the Examples to hold multiple variants; Boot 3, Bazel versions, Kotlin, etc.
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 257
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Right now the examples are inline in the workspace with the rules_spring project itself. This is nice in that changes to the rule are instantly tested with the examples.
But we don't have a good way to test/demo it against:
- different versions of Bazel
- different versions of Spring Boot
- related tech stacks, like Kotlin, rules_oci etc
without making an absolute mess of the WORKSPACE file.
We will refresh the Kotlin branch in #183 but hopefully we build a better solution in this work.
Contributor guide
No contributing guide indexed for this repository
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 the current inline examples and WORKSPACE file, then compare the proposed needs with the Kotlin branch in #183. Done means examples can cover multiple Bazel and Spring Boot versions and related stacks without making WORKSPACE unmanageable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, spring-boot
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100