-
Notifications
You must be signed in to change notification settings - Fork 159
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
Introduce more extension points and delete scopes
#10758
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
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.
Love to see the scopes go in favour of this 🥳
packages/web-app-files/src/components/FilesList/QuickActions.vue
Outdated
Show resolved
Hide resolved
packages/web-pkg/src/composables/piniaStores/extensionRegistry/types.ts
Outdated
Show resolved
Hide resolved
packages/web-pkg/src/composables/piniaStores/extensionRegistry/extensionRegistry.ts
Show resolved
Hide resolved
packages/web-app-files/tests/unit/views/spaces/GenericSpace.spec.ts
Outdated
Show resolved
Hide resolved
bdb97b6
to
dbef7a9
Compare
scopes
@dschmidt @JammingBen ready for a thorough re-review. As far as I can tell the last remaining open question is whether the files app extension points should be defined and registered via the files app or defined in |
packages/web-pkg/src/composables/piniaStores/extensionRegistry/extensionRegistry.ts
Outdated
Show resolved
Hide resolved
ae2f48b
to
66d9138
Compare
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.
LGTM 😍
@@ -207,6 +210,14 @@ export default defineComponent({ | |||
] as FileAction[] | |||
} | |||
|
|||
const actionExtensions = requestExtensions<ActionExtension>({ | |||
id: 'app.files.batch-actions', |
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.
Hmm - it's a bit weird to reference an extension point defined in an app in web-pkg ... 👀
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.
agreed. as discussed in chat: we'll tackle that in a followup.
packages/web-pkg/src/composables/piniaStores/extensionRegistry/extensionRegistry.ts
Outdated
Show resolved
Hide resolved
Quality Gate passedIssues Measures |
Description
This PR introduces more extension points, allows registering extension points through app bootstrapping and gets rid of the
scopes
property on theExtension
type.All of the changes are "under the hood", if anything is different in the UI now it's a bug in the PR.
Motivation and Context
Offer extension points throughout our platform so that extension developers can easily hook their extensions into existing extension points.
Types of changes