Statick analysis plugins for TeX/LaTeX files and projects.
Statick TeX/LaTeX Plugins
This is a set of plugins for Statick that will discover TeX/LaTeX files and perform static analysis on those files.
The current plugins will discover TeX/LaTeX files in a project and can be configured to check those files using ChkTeX and LaCheck. Custom exceptions can be applied the same way they are with Statick exceptions.
The recommended method to install these Statick plugins is via pip:
pip install statick-tex
You can also clone the repository and use it locally.
The most common usage is to use statick and statick-tex from pip. In that case your directory structure will look like the following:
To run with the default configuration for the statick-tex tools use:
statick project/ --output-directory output/ --profile tex-profile.yaml
Pip Install and Custom Configuration
There are times when you will want to have a custom Statick configuration. This is usually done to run a different set of tools than are called out in the default profile, or to add exceptions. For this case you will have to add the new Statick configuration somewhere. This example will have custom exceptions in the project, such that the directory structure is:
For this setup you will run the following:
statick project/ --output-directory output/ --user-paths project/statick-config/ --profile tex-profile.yaml
Source Install and Custom Configuration
The last type of setup will be to have all of the tools available from cloning repositories, not installing from pip. The directory structure will look like:
Using the example where we want to override the default exceptions with custom ones in the project, the command to run would be:
./statick/statick project/ --output-directory output --user-paths statick-tex,project/statick-config --profile tex-profile.yaml
Tests and Contributing
If you write a new feature for Statick or are fixing a bug, you are strongly encouraged to add unit tests for your contribution. In particular, it is much easier to test whether a bug is fixed (and identify future regressions) if you can add a small unit test which replicates the bug.
Before submitting a change, please run tox to check that you have not introduced any regressions or violated any code style guidelines.
Statick uses mypy to check that type hints are being followed properly. Type hints are described in PEP 484 and allow for static typing in Python. To determine if proper types are being used in Statick plugins the following command will show any errors, and create several types of reports that can be viewed with a text editor or web browser.
pip install mypy mkdir report mypy --ignore-missing-imports --strict --html-report report/ --txt-report report src/
It is hoped that in the future we will generate coverage reports from mypy and use those to check for regressions.
Statick code is formatted using black. To fix locally use
pip install black black src
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size statick_tex-0.2.2-py3-none-any.whl (10.9 kB)||File type Wheel||Python version py3||Upload date||Hashes View|
|Filename, size statick-tex-0.2.2.tar.gz (7.9 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for statick_tex-0.2.2-py3-none-any.whl