An open API service indexing awesome lists of open source software.

https://github.com/cpp-linter/cpp_linter_dart

experimental port of the python cpp-linter package to dart
https://github.com/cpp-linter/cpp_linter_dart

Last synced: 10 months ago
JSON representation

experimental port of the python cpp-linter package to dart

Awesome Lists containing this project

README

          

[![Dart](https://github.com/cpp-linter/cpp_linter_dart/actions/workflows/dart.yml/badge.svg)](https://github.com/cpp-linter/cpp_linter_dart/actions/workflows/dart.yml)
[![code coverage](https://codecov.io/gh/cpp-linter/cpp_linter_dart/graph/badge.svg?token=iXV4BqcvQy)](https://codecov.io/gh/cpp-linter/cpp_linter_dart)

# cpp_linter_dart

> [!NOTE]
> Archived Notes: With the new node.js bindings from [cpp-linter-rs](https://github.com/cpp-linter/cpp-linter-rs) project, the cpp_linter_dart project is completely obsolete.

This is an experimental port of the
[cpp-linter python package](https://github.com/cpp-linter/cpp-linter). Like the
python package, this dart package is not meant to be used as a importable library.
Although, some library parts may be useful to other applications. For example,
`lib/git.dart` can be used to parse a diff into a `List` that describes a file's changed lines.

This dart port is meant to optimize away any runtime compilation. By using dart, we
can ship a binary executable (native to Linux, Windows, or MacOS) instead of
downloading executable scripts from pypi.

The application entrypoint's source is in `bin/`, and the application's library code
is in `lib/`. Unit tests are in `test/` which are used to calculate code coverage and detect bugs early.