Closed imanjra closed 1 week ago
This update introduces a new function usePluginComponent
for retrieving plugin components by name, refactors the Panel
component to use a PanelNotFound
component for non-existent panels, and adds the PanelNotFound
component itself. These changes optimize plugin and panel handling.
Files | Change Summary |
---|---|
app/.../src/index.ts |
Added usePluginComponent function to fetch plugin components by name. |
app/.../src/components/Panel.tsx |
Refactored Panel component to destructure props and use PanelNotFound for missing panels. |
app/.../src/components/PanelNotFound.tsx |
Introduced PanelNotFound component to display messages for non-existent panels. |
🌟 Plugins dance in code's delight,
Panels found or lost in sight,
Components spring from functions new,
Reacting swift, our UI grew.
In this space, let's celebrate,
With joy, our app, we elevate! 🎉
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
What changes are proposed in this pull request?
Overridable panel not found component
How is this patch tested? If it is not, please explain why.
Using plugin component named
PanelNotFound
Release Notes
Is this a user-facing change that should be mentioned in the release notes?
See above
What areas of FiftyOne does this PR affect?
fiftyone
Python library changesSummary by CodeRabbit
New Features
usePluginComponent
function to retrieve plugin components by name from active plugins.PanelNotFound
component to handle scenarios where a panel is not found, displaying a custom message.Refactor
Panel
component to destructure props and utilize the newPanelNotFound
component for better error handling.