Skip to content

Conversation

@rombirli
Copy link
Contributor

No description provided.

- duplicate declaration of j
- illegal shadowing of i
- switch on / when -> if to simplify compliant solution
@tomasz-tylenda-sonarsource
Copy link
Contributor

RSPEC PR's folllow a particular naming scheme. It should be "Modify S134(apex): Add compliant example and fix non-compliant". The PR also needs a label (apex).

@rombirli rombirli added the apex label Nov 26, 2025
@rombirli rombirli changed the title apex:S134 Add compliant solution for rule S134 in Apex, fix non-compliant example Modify S134(apex): Add compliant example and fix non-compliant Nov 26, 2025
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with a comment.

@sonarqube-next
Copy link

Quality Gate passed Quality Gate passed for 'rspec-tools'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@sonarqube-next
Copy link

Quality Gate passed Quality Gate passed for 'rspec-frontend'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@rombirli rombirli added this pull request to the merge queue Nov 27, 2025
Merged via the queue into master with commit 8d7896c Nov 27, 2025
16 of 18 checks passed
@rombirli rombirli deleted the rombirli/s134-add-compliant-code-example branch November 27, 2025 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants