Yassin Kammoun

Results 65 issues of Yassin Kammoun

Reported in https://community.sonarsource.com/t/sonarqube-not-recognizing-sinon-add-at-least-one-assertion-to-this-test-case/68269

type: enhancement

Rules using type information currently don't raise any issues on inline JavaScript code in YAML files. In fact, they are automatically disabled since the parser services returned by TypeScript ESLint...

type: enhancement

- [ ] [Update analyser documentation](https://github.com/SonarSource/SonarJS/blob/master/sonar-javascript-plugin/src/main/resources/static/documentation.md#prerequisites) - [ ] [Update pom.xml Node.js minimum version](https://github.com/SonarSource/SonarJS/blob/89d21eee95f823a9b9134461e606f5f3e21593f0/sonar-javascript-plugin/pom.xml#L129) - [ ] [Update Node.js deprecation warning](https://github.com/SonarSource/SonarJS/blob/master/sonar-javascript-plugin/src/main/java/org/sonar/plugins/javascript/eslint/NodeDeprecationWarning.java) - [ ] [Update package.json engine](https://github.com/SonarSource/SonarJS/blob/ffbd89ad5cc8941f70129f6896230380041979df/eslint-bridge/package.json#L26)

S5860 is raising false positives when a matched group of a regular expression is accessed with the non-null assertion operator: ```typescript const pattern = /(?\\w)/; const matched = 'str'.matchAll(pattern); if...

type: false positive
topic: quality

S1172 currently raises false positives when a parameter occurs only in the position of a JSX identifier. This happens because ESLint context does not bind JSX identifier references to parameter...

type: false positive
topic: quality

Depends on #3231 We are currently using `[email protected]`, but we are not able to upgrade the dependency as the next version [9.0.0](https://github.com/vuejs/vue-eslint-parser/releases/tag/v9.0.0) dropped the support of Node.js 12. Furthermore, this...

Depends on #3231 As a reminder, we had to fork [yaml](https://github.com/eemeli/yaml) as it was not compatible with Node.js 12. Once we drop the support of this version, we can switch...

The rule currently limits itself to raising issues on member expressions in which the possibly nullable target object is an identifier: ```javascript var nullable = /* ... */; console.log(nullable.bar); ```...

type: enhancement
topic: quality

Reported in https://community.sonarsource.com/t/scss-css-s5362-invalid-malformed-calc-function/62691

type: false positive
topic: quality

ESLint (['semi'](https://eslint.org/docs/rules/semi)) rule, known also as S1438, currently flags statements missing semicolons on the wrong line end on some occasions. This produces misleading issue highlightings on SonarQube (see [example](https://peach.sonarsource.com/project/issues?id=goof_nodev14&issues=AX4HMu-JcYOUBzznwtq_&open=AX4HMu-JcYOUBzznwtq_)). Consider...

type: enhancement
topic: quality