-
**Add new rules to the list.**
Rules:
1. invalid gherkin file (https://github.com/gherlint/gherlint/pull/63)
2. `error`
- [x] `indentation` (https://github.com/gherlint/gherlint/pull/66)
…
-
So to make it that this is right:
```yaml
# For all rules
ignore: |
*.dont-lint-me.yaml
/bin/
!/bin/*.lint-me-anyway.yaml
rules:
key-duplicates:
ignore: |
generated
…
-
**Description**
It would be great if the `check.sh` script took an additional boolean parameter: `FAIL_ON_ERRORS`.
**Use Case**
Most linters will return exit code 0 if no errors are found, and ex…
TimD1 updated
2 weeks ago
-
Maybe it's worth coming up with our own set of lint rules (no `x => x` selectors?)
-
I'm converting our repo to use bzlmod, and I noticed a few things in the process; I'm sorry for the lack of details on some of this, I'm new to bzlmod so I can currently only point out issues, not sol…
-
Use case:
We need to onboard existing schemas that do not conform to our desired set of linting rules, but want to prevent any new non-compliant schema changes from ending up in our supergraph.
Pr…
-
For starters, we could check the scenarios that mainstream commercial tools address:
- https://www.realintent.com/clock-domain-crossing-meridian-cdc
- https://www.synopsys.com/verification/static-an…
-
- [eslint-config-standard](http://standardjs.com/)
- [eslint-plugin-import](https://www.npmjs.com/package/eslint-plugin-import)
```eslint --init``` produce the standard rules
[1](https://github…
-
Effective Dart has a rule, ["DO type annotate fields and top-level variables if the type isn't obvious"](https://dart.dev/effective-dart/design#do-type-annotate-fields-and-top-level-variables-if-the-t…
-
### Description
Thanks for such a great friend. We are together for many years, and we have developed some habits how we live together, and what we can expect from each other.
Those habits somet…