Change recommended library name#19
Conversation
📝 WalkthroughWalkthroughThe README.md file has been updated with documentation changes. The wording for Checker Framework configuration guidance has been revised from "The recommended way" to "The Gradle developers recommend". The Gradle configuration example now references the correct property path for accessing the Checker Framework version, and the library key in the gradle libs versions TOML example has been renamed to reflect the proper naming convention. These updates affect only documentation and configuration examples without modifying any functional code. 🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Line 32: Replace the non-idiomatic phrase "recommend to modify" in the README
sentence ("The Gradle developers recommend to modify two files. Add this to
`build.gradle`:") with a correct construction such as "recommend modifying" or
"recommend that you modify" so the sentence reads either "The Gradle developers
recommend modifying two files." or "The Gradle developers recommend that you
modify two files." and keep the rest of the sentence ("Add this to
`build.gradle`:") unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 21f637c2-06fa-4b5a-b861-9979b724cc96
📒 Files selected for processing (1)
README.md
No description provided.