Allow multiple extension to be registered for the same page/resource

[alecritson]

Currently when registering extensions in the panel, they are identified by the class to be extended as the array key, for example:

LunarPanel::extensions([
  CustomerResource::class => ExtensionA::class,
]);

This means you cannot register muliple extensions at once and would need to call extensions multiple times:

LunarPanel::extensions([
  CustomerResource::class => ExtensionA::class,
]);

LunarPanel::extensions([
  CustomerResource::class => ExtensionB::class,
]);

This PR looks to introduce changes so you can pass an array of extensions instead, meaning it can all be done in one call:

LunarPanel::extensions([
  CustomerResource::class => [ExtensionA:class, ExtensionB::class],
]);

Other notable tweaks

• Added a check that the extension class exists before registering to minimise exceptions
• Use app($extension) instead of new $extension to initialise the extension class.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
lunar-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 17, 2025 11:48am