Generate nice looking documents from your FIX repository.
Command-line interface
fix-parse [--base fixation/fix_repository_2010_edition_20140507] [--document] [--fiximate]
--base points to where you're storing your fix repository.
--document generates a single-page document.html suitable for turning into a pdf.
--fiximate generates fiximate-styled pages, suitable for online-publishing.
Using your own templates
The core of fixation is centered around Jinja2 templates, before you begin you should bookmark [http://jinja.pocoo.org/docs/2.10/templates/] contains well-written and easy to follow documentation on how to write templates.
Now the easiest way to get started is to copy the templates/ folder into your current working directory, there are a few base templates which contain the generic structure and then more specific templates which extends the bases.
Writing templates
In the case of --fiximate you'll have a repository which will tell you what type you're handling, the copyright and version
You also have access to the Jinja2 filter linkify (which gives you a relative link to the item) and the tests messages, field, component, and blacklist/whitelist (with or without context).
The following is how messages.html uses linkify to generate links.
<a href="{{ msgcontent | linkify }}">
The following is from how messages.html check if something is a field or component.
{% if msgcontent is component %}
The following example is from document.html and handles blacklisting/whitelisting with and without context.
{% if msgcontent is not blacklisted(message) %}
{% if message is not blacklisted %}
document-settings.json
If you want to blacklist or whitelist things there are two ways to do it, in the following example the StandardTrailer will be considered blacklisted in the context of message ResendRequest (2)
Anything put in extra_data will be inserted into the document so the following example would let you use {{ key }} to access the list.
{
"blacklist": ["0", "StandardHeader"],
"ctx_blacklist": { "2": ["StandardTrailer"] },
"extra_data": { "key": ["value1", "value2"] }
}
Metadata
Release files for FIXation 0.0.4
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 |
|---|---|---|---|---|
| FIXation-0.0.4.tar.gz | 8.8 kB | Without provenance | Details for FIXation-0.0.4.tar.gz |
Release files / FIXation-0.0.4.tar.gz
| Download URL | FIXation-0.0.4.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ecbe5d562902671e6383d84ea1e6059f08ffd74f5b78daf6d29e667f580a6dc
|
|
BLAKE2b-256 checksum How to use checksums |
4c0d9a6db21aa6bcc6c6fd9316e2dbc47f11b87180cdee6fd4efbf6101a9553a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for FIXation 0.0.4
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.