feat(astro): pass collection name to live content loaders

[ascorbic]

Changes

Live content collection loaders now receive the collection name as part of their parameters. This is helpful for loaders that manage multiple collections or need to differentiate behavior based on the collection being accessed.

export function storeLoader({
  field,
  key,
}) {
  return {
    name: "store-loader",
    loadCollection: async ({ filter, collection }) => {
      // ...
    },
    loadEntry: async ({ filter, collection }) => {
      // ...
    },
  };
}

Testing

Added tests

Docs

Need updating

[changeset-bot]

🦋 Changeset detected

Latest commit: 57eeff9

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

⚠️ Package Trust Level Decreased

Caution

Decreased trust levels may indicate a higher risk of supply chain attacks. Please review these changes carefully.

📦 Package	🔒 Before	🔓 After
eslint-plugin-regexp	trusted-with-provenance	none
@cloudflare/kv-asset-handler	trusted-with-provenance	none
@cloudflare/unenv-preset	trusted-with-provenance	none
workerd	trusted-with-provenance	none
@sveltejs/vite-plugin-svelte-inspector	trusted-with-provenance	provenance
@sveltejs/vite-plugin-svelte	trusted-with-provenance	provenance
jsdoc-type-pratt-parser	trusted-with-provenance	none
miniflare	trusted-with-provenance	none
youch	provenance	none
@cloudflare/workerd-darwin-64	trusted-with-provenance	none
@cloudflare/workerd-darwin-arm64	trusted-with-provenance	none
@cloudflare/workerd-linux-64	trusted-with-provenance	none
@cloudflare/workerd-linux-arm64	trusted-with-provenance	none
@cloudflare/workerd-windows-64	trusted-with-provenance	none
wrangler	trusted-with-provenance	none

[codspeed-hq]

Merging this PR will not alter performance

✅ 9 untouched benchmarks

---

_{Comparing loader-collection-name (57eeff9) with next (89b6cdd)¹}

Footnotes

1. No successful run was found on next (6f88013) during the generation of this report, so 89b6cdd was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩