- convert md tables to use json fields data
- replace pymdownx.snippets to include-markdown
- include-markdown allows markdownextradata to properly render
The goal of this pipeline is to assist in catching issues with changes
made to `metadata.json`. This will be especially useful to have during
pull requests, where changes can be validated before they are merged,
which will avoid breaking any tooling that depends on the
`metadata.json` file.
- NEW: CF `[x265 (no HDR/DV)]` - This blocks/ignores HD releases that are encoded in x265 **but it will allow to exclude/bypass if it has HDR and/or DV**
Currently, tooling that references files in the Trash Guides github
repository has no reliable way to know where certain information lives.
For example, the Recyclarr application hard-codes paths (relative to the
repo root) to find the location of certain JSON files for Sonarr and
Radarr. Hard-coding paths is a poor practice because it limits the
ability for the Guides repository to be reorganized without breaking
tools.
This commit introduces a file named `metadata.json` that exists at the
root of the repository. Its sole purpose is to communicate information
about the repository itself. For now, the only thing this file provides
is the paths to JSON files for Radarr custom formats and Sonarr release
profiles.
This file will never move, otherwise we run into the same issue that
existed prior to having this file. When relevant files or directories
are reorganized in the repository, respective paths in `metadata.json`
will be updated which will allow tooling to continue to find needed
resources.
The catalyst for this change is that there has been discussion recently
about a new structure for JSON files in the repository due to the
introduction of Sonarr v4 JSON files.
Lastly, a schema has been provided to assist with live editing in
`metadata.json`. The schema file is named `metadata.schema.json`. Some
editors provide validation as you edit JSON files (e.g. VS Code), which
will take advantage of this
Fixes#703
It doesn't exist yet as of this commit, but a set of new JSON files will
be placed at the root of the repo and the editor config file is needed
at the root of the repo to ensure proper formatting of those JSON files.
TRaSH
tiemonl
Robert Dailey
nuxen
Alex
userdocs
TRaSH
ItsME6969