I want to request a feature.

Typescript noUnusedParameters option ignores params beginning with underscore (understand that some people dislike this, but this is how it is). For such params that are being ignored it would seem preferable to use the optional parameter syntax over providing an unused default value. A default value makes it LESS clear that the parameter is actually not used.

When we use a rule from eslint core, we don't control which node is reported, in the case of big nodes, the resulting highlighting is ugly in the UI. Knowing that 30 more rules (see SonarSource/SonarJS#1918) will rely on eslint-core, this situation may happen again in the future.

Rules concerned

• S138 (already fixed in https://github.com/SonarSource/SonarJS/iss

Running the examples gives me:

ERROR: You must define the following mandatory properties for 'Unknown': sonar.projectKey

(which makes sense)

However, I don't know how to pass this and other properties (like properties file, branch name etc)

We are having issues connecting to our sonar and didn't know the best practice for providing our own CA. We have seen the maven resource add support for a custom certificate for a repository: nulldriver/maven-resource@26d48ad We also had in the past followed the work around done when concourse started clobbering the certs that come with

Ejercicios básicos de GIT. Situaciones anómalas

User story

As the author of generator-apiproxy,
I must ensure that all release tasks have been addressed
In order to deliver my product.

Acceptance criteria

📝 Source: npm-module-checklist

• 1. Watch the [egghead.io][egghead] series [How to Write an Open Source JavaScript Library][egghead series];
  it is extremely u