Issue in using pseudo comment "#EC EQUALS_CHAINING
Nobody has claimed this yet.
- Dominant language
- ABAP
- Stars
- 435
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
💡 Code pal for ABAP follows the Clean ABAP. If the issue relates to coding style, please submit it here.
Check Name
Equals Sign Chaining
Actual Behavior
NA
Expected Behavior
NA
Issue
After inserting the pseudo-comment "#EC EQUALS_CHAINING in the code to deactivate the finding. The result was a complaint from the SLIN code check (SE24, Extended Check). It says "The pseudo comment "#EC EQUALS_CHA is not a valid SLIN pseudo comment." and "Cannot be deactivated using a pragma. Message Code BRE 0807". The same issue was coming for pseudo comment "#EC EMPTY_CATCH but its resolved after using the pseudo comment "#EC NO_HANDLER.
Contributor guide
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 by reproducing the Equals Sign Chaining and EMPTY_CATCH pseudo-comment cases in SE24 with the SLIN code check, using the examples in the issue. Compare the pseudo-comments accepted by Code Pal for ABAP with those recognized by SLIN; done means the intended suppression no longer produces invalid-pseudo-comment or BRE 0807 messages.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100