-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question: best practice for generating LazyActionMenu list actions #12244
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/lifecycle frozen |
The request for exposing modals are partly addressed in #12785 |
I'm running into the same issue. Trying to build a page to list my CRDs and I need the same actions that we see on the details page - Edit, Delete, Edit Labels, and Edit Annotations. In the console-app, a lot of components simply use the |
I have a CRD that currently only have a details page, from where I can open an actions menu with edit and delete actions. Example:
I have created a dynamic plugin to be able to list all of my CRDs in a project, and where I want to have the action menu for each row. It seems to me that the
LazyActionMenu
component is perfect fit for this, and is simple to add:This results only in an empty action menu (i.e., it found no actions):
That is because I need to add a console.action/resource-provider. The documentation for this is sparse, and there are no examples in the dynamic-demo-plugin. And when browsing resource providers and action creators in
console/frontend/packages/console-app
, I notice that some building blocks (components and helper functions) are not exposed trough your published NPM packages. For example, the modals (e.g., the delete-modal).I then wonder if you got some examples or tip on best practices for developing (or reusing) functionality for resource-providers?
And it would be very helpful if you could publish more of the functionality/components that you use internally, e.g., the modals and reusable actions (like common-factory.ts).
The text was updated successfully, but these errors were encountered: