You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9-27Lines changed: 9 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,31 +12,21 @@
12
12
13
13
# Contributing
14
14
15
-
Contributions are encouraged! Please use the issue page to submit feature
16
-
requests or bug reports. Issues with attached PRs will be given priority and
17
-
have a much higher likelihood of acceptance. Please also open an issue and
18
-
associate it with any submitted PRs. That said, the aim is to keep this library
19
-
as lightweight as possible. Only features with broad-based use cases will be
20
-
considered.
15
+
Contributions are encouraged! Please use the issue page to submit feature requests or bug reports. Issues with attached PRs will be given priority and have a much higher likelihood of acceptance. Please also open an issue and associate it with any submitted PRs. That said, the aim is to keep this library as lightweight as possible. Only features with broad-based use cases will be considered.
21
16
22
-
We are actively seeking additional maintainers. If you're interested, please
23
-
[contact me](https://github.com/bckohan).
17
+
We are actively seeking additional maintainers. If you're interested, please [contact me](https://github.com/bckohan).
24
18
25
19
## Installation
26
20
27
-
`django-typer` uses [Poetry](https://python-poetry.org/) for environment, package, and dependency
28
-
management:
21
+
`django-typer` uses [Poetry](https://python-poetry.org/) for environment, package, and dependency management:
29
22
30
23
```shell
31
24
poetry install
32
25
```
33
26
34
27
## Documentation
35
28
36
-
`django-typer` documentation is generated using [Sphinx](https://www.sphinx-doc.org/en/master/) with the
37
-
[readthedocs](https://readthedocs.org/) theme. Any new feature PRs must provide updated documentation for
38
-
the features added. To build the docs run doc8 to check for formatting issues
39
-
then run Sphinx:
29
+
`django-typer` documentation is generated using [Sphinx](https://www.sphinx-doc.org/en/master/) with the [readthedocs](https://readthedocs.org/) theme. Any new feature PRs must provide updated documentation for the features added. To build the docs run doc8 to check for formatting issues then run Sphinx:
40
30
41
31
```bash
42
32
cd ./doc
@@ -46,11 +36,7 @@ poetry run make html
46
36
47
37
## Static Analysis
48
38
49
-
`django-typer` uses [ruff](https://docs.astral.sh/ruff/) for Python linting, header import
50
-
standardization and code formatting. [mypy](http://mypy-lang.org/) and
51
-
[pyright](https://github.com/microsoft/pyright) are used for static type checking. Before any PR
52
-
is accepted the following must be run, and static analysis tools should not produce any errors or
53
-
warnings. Disabling certain errors or warnings where justified is acceptable:
39
+
`django-typer` uses [ruff](https://docs.astral.sh/ruff/) for Python linting, header import standardization and code formatting. [mypy](http://mypy-lang.org/) and [pyright](https://github.com/microsoft/pyright) are used for static type checking. Before any PR is accepted the following must be run, and static analysis tools should not produce any errors or warnings. Disabling certain errors or warnings where justified is acceptable:
54
40
55
41
```bash
56
42
./check.sh
@@ -64,10 +50,7 @@ To run static analysis without automated fixing you can run:
64
50
65
51
## Running Tests
66
52
67
-
`django-typer` is set up to use [pytest](https://docs.pytest.org/en/stable/) to run unit tests. All the tests are
68
-
housed in `django_typer/tests/tests.py`. Before a PR is accepted, all tests
69
-
must be passing and the code coverage must be at 100%. A small number of
70
-
exempted error handling branches are acceptable.
53
+
`django-typer` is set up to use [pytest](https://docs.pytest.org/en/stable/) to run unit tests. All the tests are housed in `tests/tests.py`. Before a PR is accepted, all tests must be passing and the code coverage must be at 100%. A small number of exempted error handling branches are acceptable.
71
54
72
55
To run the full suite:
73
56
@@ -81,10 +64,9 @@ To run a single test, or group of tests in a class:
81
64
poetry run pytest <path_to_tests_file>::ClassName::FunctionName
82
65
```
83
66
84
-
For instance, to run all tests in BasicTests, and then just the
85
-
test_call_command test you would do:
67
+
For instance, to run all tests in BasicTests, and then just the test_call_command test you would do:
86
68
87
69
```shell
88
-
poetry run pytest django_typer/tests/tests.py::BasicTests
89
-
poetry run pytest django_typer/tests/tests.py::BasicTests::test_call_command
70
+
poetry run pytest tests/tests.py::BasicTests
71
+
poetry run pytest tests/tests.py::BasicTests::test_call_command
0 commit comments