{"version":"2.1.246","anchor":"storage-keys-for-marketplaces-branch-on-tree-versus-named-fi","canonical_anchor":"storage-keys-for-marketplaces-branch-on-tree-versus-named-fi","heading":"Storage keys for marketplaces branch on tree versus named-file form","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/storage-keys-for-marketplaces-branch-on-tree-versus-named-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Storage keys for marketplaces branch on tree versus named-file form\n\nMarketplace storage keys can point at whole file trees, but generic writes are refused.\n\n**What**\n\nPath resolution, key validation, child and descendant lookup, directory listing and scope enumeration in the storage key layer all check whether a marketplace key carries a relative path, and take the file-tree route if so. Writes through the tree interface are refused because trees are produced by cloning or publishing, and generic key resolution does not accept a marketplace tree yet.\n\n**Evidence**\n\n`a marketplace's tree is not resolved through resolveKey yet`\n\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}