7 Commits (1fe2b7fb7ec633c6b615e2e9108c93a0b5e74e59)

Author	SHA1	Message	Date
Robert Dailey	9c17d5fae6	Move recyclarr property up a level ... The `recyclarr` property was under `json_paths` which isn't appropriate for a few reasons: 1. `json_paths` is expected to be for guide-only data (like custom formats). 2. The recyclarr path at the moment is to YAML files, not JSON files.	2 years ago
yammes08	6c9d94c87c	Update for new recyclarr feature ... Update metadata json and schema to support recyclarr templates feature. Addes templates.json to catalog available templates. Relocate recyclarr-configs to /docs so they're in a central location.	2 years ago
TRaSH	92ed62325e	Updated: metadata	2 years ago
Robert Dailey	7f98659604	chore(metadata): Add paths for quality definition data	3 years ago
tiemonl	d0a8289f28	undo markdown changes to split PR	3 years ago
Robert Dailey	9bce114c97	chore: Fix incorrect references in metadata schema	3 years ago
Robert Dailey	a1941d691a	chore: New metadata.json file with repo information ... 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	3 years ago