-
- **Improvement:**
Enhance code formatting and Linting Standards with Pre-configured Tools ([Black](https://black.readthedocs.io/en/stable/), [Flake8](https://flake8.pycqa.org/en/latest/), [Isort](h…
-
I would like to add a feature to generate [Gitlab code quality](https://docs.gitlab.com/ee/ci/testing/code_quality.html) reports with `gdlint`.
**Example usage in .gitlab-ci.yml**
```
...
gdlint…
-
- Refactor code to make it clean and maintainable. This includes using meaningful variable names, following a consistent coding style, and breaking down large functions into smaller, more manageable o…
-
Hi,
I analyzed the VHDL code from your NEORV32 project with Linty: https://oss.linty-services.com/dashboard?id=neorv32&codeScope=overall
Do not get scared by the number of issues :-)
It's just …
-
Generalize flake8/black and any subsequent useful linter (pylint ? pyflakes ? ...) to the source code in order to increase the global quality level.
-
Currently, the project doesn't enforce consistent code style or run automated code quality checks on every commit. This can lead to inconsistent code formatting, overlooked errors, and code that doesn…
-
Hi,
I analyzed the VHDL code from your VUnit project with Linty: https://oss.linty-services.com/dashboard?id=vunit&codeScope=overall
Do not get scared by the number of issues :-)
It's just to p…
-
I've found numerous bugs in your code that I'm going to address:
- Using a section tag as a container for all the parts of the site is not a good idea in terms of best practices for several reasons…
-
This paper identifies a number of code quality issues in intro python: https://dl.acm.org/doi/10.1145/3649217.3653638
We should make sure that all are easily capturable with Pedal.
-
@nayanaamahesh We did an automated analysis of your code to detect potential areas to improve the code quality. We are sharing the results below, to help you improve the iP code further.
IMPORTANT: N…