-
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…
-
Example: `#declare score_holder FuN`
Does not raise a linting error, with this configuration: `"datapack.lint.nameOfScoreHolders": ["warning", "snake_case"]`
When the score_holder is used in a com…
-
We currently use flake8 for linting, but ruff provides a nice way to consolidate linting rules used/defined by various other tools, such as black and flake8. We should also remove the "special" lintin…
-
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…
-
We don't want to accidentally use features that are in Developer Preview or Experimental. There doesn't seem to be a way to stop this other than through manual review.
This isn't something that wil…
-
Hey folks! I'm currently using sqruff 0.19.1 installed via cargo on Windows 10 working with the DuckDB dialect. For some reason a `LOAD spatial;` is throwing off the rest of my linting rules.
```
…
-
Upon a merge into `master` (after successful testing and review), we can trigger building the docs with `sphinx` and uploading to `readthedocs`.
Thoughts:
- add a check to see if the doc sources …
-
Add linting rules for better consistency of code. Incorporate in GitHub Actions.
-
It would be useful to configure MegaLinter integration following this commonalities guideline: https://github.com/camaraproject/Commonalities/blob/4d05a3dbf1c9b61d3ec42eed117d78e6b7645d82/documentatio…
-
This might sometimes be what you want, but it's worth noting that
* the ruff rules are pretty strict and include automatically fixing a lot of issues. This is very much a matter of taste, but I perso…