Changelog

v0.0.2 (2023-03-14)

Fix

Rtd python version too old (``6dc74bf` <https://github.com/cuinixam/candiy/commit/6dc74bf00a759298bee0bce27476bf907e16b360>`_)

v0.0.1 (2023-03-14)

Fix

Fix all pre-commit checks reported problems (``1bb3760` <https://github.com/cuinixam/candiy/commit/1bb376021d8b2b0591b695ba51c84a12ec13dc73>`_)

Documentation

Add tasks info to README.md (``c317071` <https://github.com/cuinixam/candiy/commit/c31707147629e621a8b6b3834a9c55e8cb022038>`_)

Contributing

Contributions are welcome, and they are greatly appreciated! Every little helps, and credit will always be given.

You can contribute in many ways:

Types of Contributions

Report Bugs

Report bugs to our issue page. If you are reporting a bug, please include:

Your operating system name and version.
Any details about your local setup that might be helpful in troubleshooting.
Detailed steps to reproduce the bug.

Fix Bugs

Look through the GitHub issues for bugs. Anything tagged with “bug” and “help wanted” is open to whoever wants to implement it.

Implement Features

Look through the GitHub issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.

Write Documentation

candiy could always use more documentation, whether as part of the official candiy docs, in docstrings, or even on the web in blog posts, articles, and such.

Submit Feedback

The best way to send feedback our issue page on GitHub. If you are proposing a feature:

Explain in detail how it would work.
Keep the scope as narrow as possible, to make it easier to implement.
Remember that this is a volunteer-driven project, and that contributions are welcome 😊

Get Started!

Ready to contribute? Here’s how to set yourself up for local development.

Fork the repo on GitHub.

Clone your fork locally:

$ git clone git@github.com:your_name_here/candiy.git

Install the project dependencies with Poetry:
```
$ poetry install
```
Create a branch for local development:
```
$ git checkout -b name-of-your-bugfix-or-feature
```
Now you can make your changes locally.
When you’re done making changes, check that your changes pass our tests:
```
$ poetry run pytest
```
Linting is done through pre-commit. Provided you have the tool installed globally, you can run them all as one-off:
```
$ pre-commit run -a
```
Or better, install the hooks once and have them run automatically each time you commit:
```
$ pre-commit install
```
Commit your changes and push your branch to GitHub:
```
$ git add .
$ git commit -m "feat(something): your detailed description of your changes"
$ git push origin name-of-your-bugfix-or-feature
```
Note: the commit message should follow the conventional commits. We run ``commitlint` on CI <https://github.com/marketplace/actions/commit-linter>`_ to validate it, and if you’ve installed pre-commit hooks at the previous step, the message will be checked at commit time.
Submit a pull request through the GitHub website or using the GitHub CLI (if you have it installed):
```
$ gh pr create --fill
```

Pull Request Guidelines

We like to have the pull request open as soon as possible, that’s a great place to discuss any piece of work, even unfinished. You can use draft pull request if it’s still a work in progress. Here are a few guidelines to follow:

Include tests for feature or bug fixes.
Update the documentation for significant features.
Ensure tests are passing on CI.

Tips

To run a subset of tests:

$ pytest tests

Making a new release

The deployment should be automated and can be triggered from the Semantic Release workflow in GitHub. The next version will be based on the commit logs. This is done by python-semantic-release via a GitHub action.

Readme

License

GUI to monitor a CAN network and communicate with an ECU.

Installation

Install this via pip (or your favourite package manager):

pip install candiy

Start developing

The project uses Poetry for dependencies management and packaging. Make sure you have it installed in your development machine. To install the development dependencies in a virtual environment, type:

poetry install

This will also generate a poetry.lock file, you should track this file in version control. To execute the test suite, call pytest inside Poetry’s virtual environment via poetry run:

poetry run pytest

Check out the Poetry documentation for more information on the available commands.

For those using VS Code there are tasks defined for the most common commands:

install development dependencies
run tests
run all checks configured for pre-commit
generate documentation

See the .vscode/tasks.json for more details.

Committing changes

This repository uses commitlint for checking if the commit message meets the conventional commit format.

Contributors ✨

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!

Credits

This package was created with Copier and the browniebroke/pypackage-template project template.

The icons were created from Tabler Icons.