Gilles Querret

Make sure you recompile all rcode with relativePaths="false". Once again, I've tried that on a very simple project, but I've been able to compile with PCT and use breakpoints in...

It can be detected, but that will trigger false positives on some codebase (I'm sure there is at least one app on Earth that considers that having named parameters starting...

> Is the double & something that could be detected by a rule ? The InvalidNamedParameter rule does this kind of check on named include parameters.

Probably related to #886. I'll work on that next week.

Can you try the SonarLint version from [this comment](https://github.com/Riverside-Software/sonar-openedge/issues/886#issuecomment-848590886) ?

Do you have your rcode mostly in PL files ? Or as .r files in a directory ?

@cverbiest You can try this version of the OE plugin: https://ci.rssw.eu/job/sonar-openedge/job/bugfix%252FSOE-886-SonarLint/ The modification is done at the analyzer level, not at the SonarLint level ; you can keep the previous...

This is being worked on at the SonarLint level. News will posted as soon as a stable version is available.

The "No TypeInfo found" messages are shown when Proparse can't find the rcode for a class reference. There's still a pending change in the SonarLint dev branch, I'll try to...

Fixed in 2.16.