{"version":"2.1.228","anchor":"extraknownmarketplaces-merges-instead-of-being-replaced","canonical_anchor":"extraknownmarketplaces-merges-instead-of-being-replaced","heading":"extraKnownMarketplaces merges instead of being replaced","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/extraknownmarketplaces-merges-instead-of-being-replaced","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### extraKnownMarketplaces merges instead of being replaced\n\nextraKnownMarketplaces now merges across settings files instead of one layer wiping the others.\n\n**What**\n\nThe `extraKnownMarketplaces` setting is now deep-merged across settings layers, so a project or managed-policy file can add a plugin marketplace without wiping out the ones defined at user or enterprise level.\n\n**Details**\n\n- Both settings-merge paths were changed; previously the highest-precedence layer replaced the whole object.\n\n**Evidence**\n\n`extraKnownMarketplaces`\n\n- Area: Plugins\n- Names: `extraKnownMarketplaces`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}