1. The users of this style guide will probably expect that all of the rules that it prescribes will be enforced by eslint. However, this is not the case - there is a secret, non-documented segmentation where some rules are enforced and others are not, because they would be "too noisy on a legacy codebase". An example of a problematic rule like this is covered in issue #2020. I propose that all of

Expected behavior

Disable an annoying clang-tidy warning on linux

Steps to reproduce

1. Create a source file containing strncpy()
2. Observe that neomake complains
3. There is no way to disable this warning globally

In this case I would need to pass --checks=-clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling to clang-tidy

Adding this as args for the c ma

The docs pages for the rules should mention each rule's default.

Otherwise the only way to know is to inspect the code.

A few restrictions are supported for “holes” already.
A search for alphanumeric characters and punctuation can be specified by a syntax which is slightly different from other filter possibilities.

I imagine that advanced filters could be specified directly after the match identifier.

• Character class
• Regular expression
• Predefi

Would it be possible to prevent outputting invalid CSS properties that would fail a CSS syntax validation plugin such as csstree/stylelint-validator?

An example of this would be when using a mixin:

const example = css`
  ${({ height }) => height ? `height: ${height};` : ''}
  width: 100%;
`;

which the processor might output

"Require calls will work only in Node.js, and will cause errors for anyone trying to use the ruleset in the browser. If your ruleset is definitely going to only be used in the context of NodeJS then using them is ok, but if you are distributing your rulesets to the public we recommend avoiding the use of require() to increase portability."

I have a extensions.js file that has functions I reuse

Starting Gradle 5.1 it is possible to pin repository to specific artefact. Plugin should check Gradle version and add a repository configuration for ktlint. This should simplify plugin setup.

Docs to look into: https://docs.gradle.org/current/javadoc/org/gradle/api/artifacts/repositories/MavenArtifactRepository.html#mavenContent-org.gradle.api.Action-

This snippet allows you to swap between languages servers:

function! SwapLanguageServer(config)
  LSClientDisable
  for [filetype, config] in items(a:config)
    call RegisterLanguageServer(filetype, config)
  endfor
  LSClientEnable
endfunction
command! Tailwind :call SwapLanguageServer(g:tailwind_server_config)
command! JS :call SwapLanguageServer(g:javascript_server_config)

• Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
• Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
• Use of conventional-commit standard going forward
• Advice not to include any package-lock.json changes PRs, for security reasons. File will be regene

Is this a request for help?:
No.

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

We just re-enabled gitlint at Zulip and a lot of our new students (we are participating in Google Code-in) who aren't comfortable with regex are confused by our ^(.+:\ )?[A-Z].+\.$ rule.

I was thinking if gitlint could show a user-defined note explaining their project's commit title style? I guess we only want to show it once if title-match-regex failed >= 1 time.

I could implement this if

see http://ember-concurrency.com/docs/tutorial (scroll down to Version 4)

Bad:

actions: {
  async handleClick() {
    // ...
  }
}

actions: {
  handleClick() {
    return something.then(() => { /* ... */ });
  }
}

@action
async handleClick() {
  // ...
}

@action
handleClick() {
  return something.then(() => { /* ... */ });
}
``

Project References help us to build specic package.

Currently, we need to build before developing a specifc package.

cd <project-root>
yarn run build

We need to enforce \n for line breaks.

Currently flakehell does not allow to show current version:

» flakehell --version
baseline  | Run patched flake8 against the code.
code      | Show plugin name and message for given code.
codes     | Show available codes and messages for given plugin.
lint      | Run patched flake8 against the code.
missed    | Show patterns from the config that has no matched plugin installed.
plu

As the title says, the ruleset.xml.example file seems out of date:

• Missing at least one "policy code" (if not more)
• Missing various customizable ruleset properties.

Would be useful to provide descriptive text of the files generated by nf-core create and the 'best practices' incorporated in the nf-core template.