[yavuzmeteafsar]

What does this change?

filee formats and filee formats <format> accept --json, so front ends don't depend on the wording of the text output. Follow-up to #582.

filee formats --json:

{ "formats": [ { "id": "png", "name": "PNG", "category": "image", "extensions": ["png"], "writable": true }, ... ] }

filee formats zip --json (the same fields, plus the two lines of the text output):

{ "id": "zip", "name": "ZIP", "category": "archive", "extensions": ["zip", "wbpz"], "writable": true,
  "targets": [...], "withEngines": ["7z", "tar", "tgz", "tbz2", "txz", "folder"] }

targets is "converts to", withEngines is "With optional engines". category is lower case like state in convert --json. The text output is unchanged.

Type of change

• Bug fix
• New feature or improvement
• New format or engine
• Translation
• Documentation
• Build, CI or dependencies

How was it tested?

• dotnet format (on the changed files)
• dotnet test (tests/Filee.Cli.Tests, filter Formats|Archives_list_folder: 10 passed). New: Formats_json_lists_every_format, Formats_json_of_one_format_matches_the_text
• Tried it: formats zip --json on macOS, Apple Silicon (dev build without 7-Zip, so the archive targets are under withEngines)

Checklist

• The PR does one thing

[yavuzmeteafsar]

The linux-x64 portable job failed on StallWatchTests.A_program_that_keeps_reporting_runs_well_past_the_stall_limit (Filee.Engines.Tests), not on this change: it is timing-based (300 ms stall limit, failed after 358 ms) and passed on linux-arm64 and Windows in the same run. The CLI tests didn’t get to run on x64 because the loop stops at the first failing project; on arm64 they passed. “Package on Ubuntu 22.04 (linux-x64)” failed only because that package wasn’t built. Could you re-run the failed jobs?

[KnifeLemon]

Thanks, @yavuzmeteafsar! The JSON follows the text output exactly, category is lower case like state in convert --json, and the help text names the flag. The earlier linux-x64 failure was the StallWatchTests timing test, as you said; the rerun passed.

@SeoJCalive is picking up the rest of #753 (presets --json and failure reasons in convert --json) in the same shape.