{"version":"2.1.239","anchor":"clearer-marketplace-validation-errors","canonical_anchor":"clearer-marketplace-validation-errors","heading":"Clearer marketplace validation errors","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/clearer-marketplace-validation-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Clearer marketplace validation errors\n\nMarketplace validation errors now name the bad source and tell you how to fix it.\n\n**What**\n\nA bare plugin source in a marketplace file now fails with a message naming the source and telling you to either use a `.\/relative\/path` or set `metadata.pluginRoot`. Reserved plugin names are also checked against a single table now instead of one rule per name.\n\n**Details**\n\n- Reserved names covered by the table: `inline`, `builtin` and `skills-dir`.\n- Full message: `Bare source name \"${b}\" requires metadata.pluginRoot. Use \".\/relative\/path\", or set metadata.pluginRoot (e.g. \".\/plugins\") to allow bare names.`\n\n**Evidence**\n\n`Bare source name \"${b}\" requires metadata.pluginRoot. Use \".\/relative\/path\", or set metadata.pluginRoot (e.g. \".\/plugins\") to allow bare names.`\n\n- Area: Plugins\n- Names: `metadata.pluginRoot`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}