A request is the code-review comment sentence that tells the author what change to make. Use concise transformation verbs such as rename, remove, consolidate, expand, fix, rewrite, move, or reorganize. State the desired end condition so the author can recognize completion. section 6.1.3
Compose a change request with the Triple-R pattern:
- Request: state what the author should do. section 6.1.3
- Rationale: explain why the change is warranted, adding references or links when useful. section 6.1.3
- Result: describe a measurable end state, such as a metric, screenshot, or target code shape. section 6.1.3
needs change: Can we update this endpoint to use version 3 (v3)? The call to our getCoordinates() method currently references version 2 (v2), a soon- to-be-deprecated (link) version, which will cause functionality to break. Also, our other endpoints are already using v3; updating this will keep our code consistent.
Shows a request that names the version change, explains the deprecation risk, and connects the fix to consistency across endpoints. section 6.1.3
