{"version":"2.1.290","anchor":"from-link-refusal-json-gains-a-requested-field","canonical_anchor":"from-link-refusal-json-gains-a-requested-field","heading":"Refusals from --from-link can include another spelling of the name","tier":"notice","area":"Startup","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/from-link-refusal-json-gains-a-requested-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Refusals from `--from-link` can include another spelling of the name\n\nWhen the hidden --from-link option refuses, its JSON output can now include a requested field holding another spelling of the name\n\n**What**\n\n`--from-link` is a hidden option, meaning it does not appear in the help text. When it refuses a request, it prints a short report in JSON, a structured text format that programs can read. That report used to hold only `kind`, `name` and `folder`. It can now also hold `requested`, which gives another spelling of the name.\n\n**Why**\n\nThis matters if you have a script or program that adds marketplaces this way and reads the report.\n\n- Area: Startup\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}