ninja-bear-distributor-fs
This ninja-bear plugin provides the possibility to distribute generated files to other locations on the file system.
distributors: # Specifies which distributor plugins to load.
# -------------------------------------------------------------------------
# Property description for ninja-bear-distributor-fs.
#
# distributor (required): ninja-bear-distributor-fs
# as (required): Specifies how the distributor will be referenced
# at the language level (in this case fs).
# paths (required): Path or list of paths (relative or absolute) to
# copy the configs to.
# create_parents (optional): If true, parent directories will be created if
# they don't exist.
# ignore (optional): If true, the section gets ignored.
# -------------------------------------------------------------------------
- distributor: ninja-bear-distributor-fs
as: fs
paths:
- ../configs/configs-1
- ../configs/configs-2
create_parents: true
languages:
- language: ninja-bear-language-examplescript
distributors: # Specifies which distributor plugins to use for the language.
- fs
properties:
- type: bool
name: myBoolean
value: true
- type: int
name: myInteger
value: 142
- type: float
name: myFloat
value: 322f # Float with float specifier. However, an additional specifier (f) is not required and will be trimmed.
- type: float
name: myCombinedFloat
value: ${myInteger} * ${myFloat} # Number and boolean combinations get evaluated during the dump process.
- type: double
name: myDouble
value: 233.9
- type: string
name: myString
value: Hello World
hidden: true # If a property should act as a helper but should not be written to the generated file, it must be marked as 'hidden'.
- type: regex
name: myRegex
value: Test Reg(E|e)x
comment: Just another RegEx. # Variables can be described using the comment property.
- type: string
name: mySubstitutedString
value: Sometimes I just want to scream ${myString}! # To use the value of another property, simply use its name with ${}. E.g., ${myString}.
Metadata
Release files for ninja-bear-distributor-fs 0.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 | |
|---|---|---|---|---|
| ninja_bear_distributor_fs-0.1.0.tar.gz | 5.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ninja_bear_distributor_fs-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.7 kB
Release files / ninja_bear_distributor_fs-0.1.0.tar.gz
| Download URL | ninja_bear_distributor_fs-0.1.0.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c4e1cda20a82f80b017666b49477e04e271a995af8b1eac1c3d37a69e87061d
|
|
BLAKE2b-256 checksum How to use checksums |
4a8621a28709fb1bc1a573d11eee57cd9779745ab2a4d5475a4b8360f2f4db08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / ninja_bear_distributor_fs-0.1.0-py3-none-any.whl
| Download URL | ninja_bear_distributor_fs-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87916533e56e57b1f11188e31e9272a3e5a0e01e9568ab9f9e09c7ac338774e9
|
|
BLAKE2b-256 checksum How to use checksums |
e48e860a3d3f765d084b1c420ff4f5f9f91ff2d32c16b4c20fa0acbe177faf9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for ninja-bear-distributor-fs 0.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.