PR analytics passed but failed in main branch scanning

Must-share information (formatted with Markdown):

  • which versions are you using: SonarQube v9.9.5 (build 90363)
  • how is SonarQube deployed: Docker

We have modified an arrow function in a typescript file in a PR, basically adding the parameters from 7 to 8, but in the PR analytics it passed, however after it’s merged to main branch, the scanning failed in main branch with this major issue:
[Arrow function has too many parameters (8). Maximum allowed is 7.]

Can someone help to explain why it passed in PR analytics but failed in main branch scanning, thanks a lot! :slight_smile:

Hi,

Welcome to the community!

I have a few questions. :slight_smile:

First, was the change recognized as ‘new’ in the PR analysis?

Is the arrow function split over multiple lines?

Could you share a screenshot of the issue that was finally raised after merge, redacted as necessary? Specifically, I want to see where the issue highlight lands in/on the function. We deliberately don’t report issues on non-new code in PR analysis, and I’m wondering if this is about how/where the issue is reported maybe causing it to be wrongly excluded.

 
Thx,
Ann