False positive in rule typescript:S7749 ("Invalid group length in numeric value")

Thilo · October 2, 2025, 2:02pm

I am using SonarCloud to analyze several repositories containing TypeScript code.

Apparently on 2025-09-22 the typescript:S7749 rule (“Numeric literals should use consistent digit grouping with separators”) was added to the built-in “Sonar way” quality profile. Since then this rule has triggered lots of false positives in many TypeScript files which use an underscore character “_” to format numeric literals. Here is an example code snippet:

expect(DEFAULT_BATCH_CONFIG).toEqual({
delayBetweenBatches: 1_000
})

SonarCloud raises a warning about the “delayBetweenBatches: 1_000”:

Invalid group length in numeric value.
Numeric literals should use consistent digit grouping with separators typescript:S7749
Software qualities impacted: Maintainability Low

The same happens for dozens of other numbers which in my opinion all are correctly formatted using an underscore separator between thousand groups (e.g. 5_000 and 10_000). Several colleagues double-checked and confirmed that these numbers look just fine and that apparently this rule is causing false positive alerts.

Could someone please confirm if there is indeed a bug in this rule? If so, could it please be fixed?

victor.diez · October 3, 2025, 3:32pm

Hello @Thilo,

could you please provide a file which raised an issue in this file? We have not been able to spot these FPs.

Thilo · October 7, 2025, 10:50am

Hello Victor,

Thanks for your reply. Here is an example repository: GitHub - markupai/content-guardian-action

The SonarCloud analysis for the main branch currently shows 21 issues for the “Invalid group length in numeric value (typescript:S7749)” rule, all of them false positives in my opinion.

Here are three concrete examples:

github.com/markupai/content-guardian-action

src/utils/error-utils.ts

main


      
            baseDelay: number
            maxDelay: number
            backoffMultiplier: number
          }
          
          /**
           * Default retry configuration
           */
          export const DEFAULT_RETRY_CONFIG: RetryConfig = {
            maxRetries: 3,
            baseDelay: 1_000,
            maxDelay: 10_000,
            backoffMultiplier: 2
          }
          
          /**
           * Error types for better error handling
           */
          export class GitHubAPIError extends Error {
            constructor(
              message: string,

github.com/markupai/content-guardian-action

src/services/api-service.ts

main


      
            const progress = batchResponse.progress
            const completed = progress.completed
            const failed = progress.failed
            const total = progress.total
          
            if (completed > 0 || failed > 0) {
              core.info(
                `📊 Batch progress: ${completed}/${total} completed, ${failed} failed`
              )
            }
          }, 2_000) // Update every 2 seconds
          
          // Wait for completion
          const finalProgress = await batchResponse.promise
          
          // Clear progress monitoring
          clearInterval(progressInterval)
          
          // Process results
          const results: AnalysisResult[] = []
          for (const [index, batchResult] of finalProgress.results.entries()) {

github.com/markupai/content-guardian-action

tests/error-utils.test.ts

main


      
          
              expect(endTime - startTime).toBeGreaterThanOrEqual(5) // Allow some tolerance
            })
          })
          
          describe('calculateBackoffDelay', () => {
            it('should calculate exponential backoff delay', () => {
              const config: RetryConfig = {
                maxRetries: 3,
                baseDelay: 1_000,
                maxDelay: 5_000,
                backoffMultiplier: 2
              }
          
              expect(calculateBackoffDelay(1, config)).toBe(1_000)
              expect(calculateBackoffDelay(2, config)).toBe(2_000)
              expect(calculateBackoffDelay(3, config)).toBe(4_000)
            })
          
            it('should respect max delay limit', () => {
              const config: RetryConfig = {

Please let me know if you need more examples or information to reproduce the problem.

victor.diez · October 9, 2025, 12:03pm

Hi @Thilo,

thanks for the samples. We have now a fix that should land in the next release of the JS/TS analyzer.

Topic		Replies	Views
False positive on Typescript - No magic number Report False-positive / False-negative...	3	1095	April 27, 2020
False Positive : S109 at Typescript static attribute SonarQube Cloud typescript	2	1359	February 26, 2021
31 new rules for TypeScript Sonar Updates javascript , typescript	2	2918	May 26, 2020
Typescript 3.7.2 Null conditional operator on a function call is giving a false positive SonarQube Cloud typescript , sonarqube-cloud	8	4120	July 8, 2020
Sonarcloud/SonarJS static analysis fails for typescript files that contains the '•' character SonarQube Cloud javascript , sonarqube-cloud	13	1695	November 28, 2019

False positive in rule typescript:S7749 ("Invalid group length in numeric value")

Related topics