salesforce / salesforce/rules_spring
Optimize IDE experience for Spring Boot iterative development
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 257
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
The current IDE experience with Spring Boot is not great. Editing a class that gets consumed in a Spring Boot app can cause long build pauses.
Work with the sharp people on the Bazel Eclipse (BEF) team (hey, that's us!) to figure out strategies to make Spring Boot iterative development faster. Let's track the ideas on the BEF Issue:
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 with the linked Bazel Eclipse (BEF) Optimize Spring Boot issue #213, where the ideas are being tracked. Review the reported IDE build pauses and the discussion there; done would require a decided, actionable strategy for faster Spring Boot iterative development.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spring-boot
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100