web Introduce more extension points and delete `scopes`

Introduce more extension points and delete `scopes`

Open kulmann opened this issue 1 year ago • 3 comments

Description

This PR introduces more extension points, allows registering extension points through app bootstrapping and gets rid of the scopes property on the Extension 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

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests
[ ] Documentation
[ ] Maintenance (e.g. dependency updates or tooling)

Apr 09 '24 19:04 kulmann

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.

Apr 09 '24 19:04 update-docs[bot]

@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 web-pkg and registered via the runtime... I added all extension point ids to the dev docs, so we might as well say that that's the source of truth for existing extension point ids. But might also be a good idea to have the extension point objects available in other apps. What do you think?

Apr 24 '24 05:04 kulmann