-
Notifications
You must be signed in to change notification settings - Fork 19
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
Allow ZAC extensions to define additional items for the "More Actions" drop down #324
Conversation
rgallettonf
commented
Apr 25, 2024
- refactored header component "requestActions()" functions to emit generic actions to support extension service actions
- added No-Op functions for forms that don't require additional "More Actions" items
…" drop down * refactored header component "requestActions()" functions to emit generic actions to support extension service actions * added No-Op functions for forms that don't require additional "More Actions" items
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
would it be possible to make a sample and document how this kind of extension would work? maybe point to some angular doc/links that cover it, that sorta thing? |
@@ -28,6 +28,7 @@ | |||
(dataChange)="dataChanged($event)" | |||
> | |||
<ng-content select="[slot=provider]" slot="provider"></ng-content> | |||
<ng-content select="[slot=registration]" slot="registration"></ng-content> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we spoke live about making these sorts of things more generic and thinking about pages as "layouts" not as "openziti" vs "specific" extensions. for example, "registration" slot is very specific. it'd be better, imo, as somethinglike "column 2, slot 1" or something like that...
Updated PR with extension service example & README.md Updated edge router extension/project slots to use more generic naming |