-
In the effort to return better errors we need to make sure that we are wrapping errors properly. One part of it is that we wrap errors properly. This means using the correct format when wrapping erro…
-
Perhaps would be good if on pull-request, the source branch must pass some markdown lint tests
-
**Describe the bug**
1. We want to have consistent coding standards for our repositories.
2. To do this we added linting to our automated processes.
3. On certain conditions husky commits and fi…
-
# Context
The goal of this ticket is to implement linting on the code. We have noticed that certain rules applied to demcompare are not applied in the test files of xDEM.
Examples of errors present…
-
### box.linters version
0.10.5
### Sample source code to lint
Assume test.R is a file with the below box import statement and 01_example.R is some file that exports stuff.
Sometimes it's u…
-
### What it does
This is analogous to already stable lint `option_as_ref_deref`. It should suggest using `Result::as_deref[_mut]` instead of `Result::as_ref` followed by `Result::map(fn preforming de…
-
What are the current thoughts on adding code linter support?
Here are some potentially useful ones:
- [black](https://github.com/psf/black) - really nice because it forces all programmers on the p…
-
Could use some standardization and some dev environment hook setups to keep the code structure clean
-
GitHub Actions can provide a quick and easy way to run builds for the project.
Additionally, in future, a action can be setup to also check/validate sqlc code.
-
I would add some:
- ~~containedctx: [thoughts](https://github.com/nspcc-dev/neo-go/issues/3026#issuecomment-1569124458)~~ (see https://github.com/nspcc-dev/neofs-node/issues/1911)
- ~~contextcheck: …