kpumuk opened a new pull request, #3726:
URL: https://github.com/apache/thrift/pull/3726

   <!-- Explain the changes in the pull request below: -->
   
   Enable `Lint/RedundantStringCoercion` and the safe `Style/Redundant*` cops 
for assignments, exceptions, freezing, interpolation, parentheses, explicit 
`self`, and string escapes.
   
   The autocorrections remove unnecessary intermediate assignments, coercions, 
receivers, grouping, and escaping while preserving behavior across the Ruby 
library, specs, integration tests, and tutorial code.
   
   `Style/RedundantBegin` and `Style/RedundantReturn` remain separate follow-up 
changes. `Style/RedundantPercentQ` is intentionally not enabled.
   
   This follows the merged ambiguity PR #3725; its diff contains only the 
general redundancy layer.
   
   
   <!-- We recommend you review the checklist/tips before submitting a pull 
request. -->
   
   - [ ] Did you create an [Apache 
Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket?  
([Request account here](https://selfserve.apache.org/jira-account.html), not 
required for trivial changes)
   - [ ] If a ticket exists: Does your pull request title follow the pattern 
"THRIFT-NNNN: describe my issue"?
   - [x] Did you squash your changes to a single commit?  (not required, but 
preferred)
   - [x] Did you do your best to avoid breaking changes?  If one was needed, 
did you label the Jira ticket with "Breaking-Change"?
   - [ ] If your change does not involve any code, include `[skip ci]` anywhere 
in the commit message to free up build resources.
   
   <!--
     The Contributing Guide at:
     https://github.com/apache/thrift/blob/master/CONTRIBUTING.md
     has more details and tips for committing properly.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to