Trelent CLI
Welcome to the Trelent CLI (Command Line Interface)! The Trelent CLI let's you offload documentation to us in a much more direct manner - we'll document an entire project all at once on your behalf. No more generating docstrings for individual functions!
Usage
Before using the CLI, you have to authenticate it using your Trelent API Key, which can be found on our Dashboard. Please note that use of the Trelent-CLI is a paid feature and is unavailable unless you upgrade your account to a paid tier.
Please note that the auth command stores your Trelent API Key locally in plain text. We are working on an improved solution and apologize for any inconvenience.
Authenticate to Trelent using the command below, and follow the prompts:
trelent auth
You may also passs your Trelent API Key directly into other commands by using the --key (-k for short) option:
trelent document -k sk_trlnt_... [FOLDER_PATH]
Once authenticated, you may generate documentation for all source code files in a given folder:
trelent document [FOLDER_PATH]
By default, docstrings will be added to a .diff file next to source. For example, a file called test.py:
def add_nums(num1, num2):
return num1 + num2
We generate test.py.diff:
def add_nums(num1, num2):
+ """Docstring here"""
return num1 + num2
If you wish to insert docstrings directly into your source files, use the --insert (-i for short) flag:
trelent document -i [FOLDER_PATH]
We offer verbose output if you want some insight into why functions or files were skipped. Use the --verbose (-v for short) flag:
trelent document -v [FOLDER_PATH]
License
Please see the LICENSE file for specific license terms. The summary below is a not legally binding.
We use the “Commons Clause” License Condition v1.0 in combination with the MIT License. You may freely view, modify or otherwisse interact with our software but can not sell it.
Metadata
Release files for trelent 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| trelent-1.0.tar.gz | 8.5 kB | Without provenance | Details for trelent-1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| trelent-1.0-py3-none-any.whl | Python 3 | none | any | Details for trelent-1.0-py3-none-any.whl |
Total release size: 17.4 kB
Release files / trelent-1.0.tar.gz
| Download URL | trelent-1.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ffff9c5c75a382a2dcc4ee50edca138219bf0e4833cf7d9edb74555b6f1ee9b
|
|
BLAKE2b-256 checksum How to use checksums |
baaffd4891c4c95216f4a801afc315df8fee0f38f3ec4b7b988a8fa35e16fb16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Release files / trelent-1.0-py3-none-any.whl
| Download URL | trelent-1.0-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e9a2e3ec8dd2eac7c39d9fabdb138958ae947aaa42ea34542c628ff9e36b292c
|
|
BLAKE2b-256 checksum How to use checksums |
c082c3e7b5f401f3feb331a08819e9b9c966d943ca0acbd3a5e70ff8c3f3fa24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Security for trelent 1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.