fix(dashboard): add entity to DetailPage

[LucidityDesign]

Description

When adding a page block via defineDashboardExtension the context.entity is received from the page component. Without this change context.entity is undefined.

Breaking changes

None

Screenshots

You can add screenshots here if applicable.

Checklist

📌 Always:

• I have set a clear title
• My PR is small and contains a single feature
• I have checked my own PR

👍 Most of the time:

• I have added or updated test cases
• I have updated the README if needed

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vendure-storybook	Ready	Preview, Comment	Feb 17, 2026 1:20pm

[vendure-ci-automation-bot]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The change adds an entity prop to the Page component in the detail-page module. The Page component usage is updated to pass entity data as an additional parameter, making it accessible to downstream components in the component tree. This modification involves a single line addition and removal in the detail-page.tsx file.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title says 'fix' but the objectives indicate this is a feature addition, not a bug fix. The title itself accurately describes what was changed (adding entity to DetailPage), but the type prefix is incorrect.	Change the title prefix from 'fix' to 'feat' to accurately reflect that this is a feature addition, not a bug fix: 'feat(dashboard): add entity to DetailPage'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Description check	✅ Passed	The PR description follows the template with clear summary, breaking changes section, and completed checklist items.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[LucidityDesign]

Sidenote: I have a special usecase where the create mutation returns more data than the get query. So it would be nice to have a way to skip the "get", because the create mutation already returns all the data that I need.

E.g.

mutation createApiKey {
   id
   ...
   unhashedKey
}

query apiKey {
   id
   ...
   # unhashedKey is only available during create
}

[LucidityDesign]

I have read the CLA Document and I hereby sign the CLA