{"version":"2.1.228","anchor":"plugin-marketplace-and-config-code-passes-a-storage-handle-e","canonical_anchor":"plugin-marketplace-and-config-code-passes-a-storage-handle-e","heading":"Plugin, marketplace and config code passes a storage handle explicitly","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/plugin-marketplace-and-config-code-passes-a-storage-handle-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Plugin, marketplace and config code passes a storage handle explicitly\n\nPlugin, marketplace and config operations now receive the session's storage explicitly instead of reaching for a global.\n\n**What**\n\nMarketplace listing and updating, plugin enable, disable and install, installed-plugin migration, config saving, stats rebuild, feedback drafts and the resume flow now take the session's storage handle as an argument instead of reading a module-level singleton.\n\n**Details**\n\n- Fetching a marketplace by URL was split: one function returns the fetched data, a separate one writes it to the cache.\n\n**Evidence**\n\n`Saving marketplace to cache`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}