Skip to content

Super scary extension development improvments. #259

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

Open
wants to merge 21 commits into
base: develop
Choose a base branch
from

Conversation

yuri-kiss
Copy link
Member

Resolves

This could be used to resolve issues with the JSON extension where it returns values that contain null / undefined.

Proposed Changes

Export's a bunch of stuff (lazily) and add's more Casting utility's.
This also add's support for sandboxed extensions to call extensionManager.refreshBlocks and extensionManger.loadExtensionIdSync; with parity changes added to the unsandboxed runtime to include these functions as-well.

Reason for Changes

Allows for extensions to access internal classes and utility's a lot easier.
Extra casting stuff was added for adding a centralized area for thoe's type of casts. (mainly meant for the JSON & BigInt extension)

-# Super scary require function export is uhh because it is useful to have it in userscripts and alike, and there is no good reason not to add an even scarier way to get it I guess.

@yuri-kiss
Copy link
Member Author

@GarboMuffin @CubesterYT if you could take a peek when you have time.

@@ -130,6 +130,42 @@ class ExtensionManager {
dispatch.setService('extensions', createExtensionService(this)).catch(e => {
log.error(`ExtensionManager was unable to register extension service: ${JSON.stringify(e)}`);
});

// Allow for sandboxed extensions, and worker extensions to access some of our APIs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'll just say right away that extending worker extensions with more powers is probably just not going to happen; if anything these are getting removed entirely

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know they are going to get removed but they exist right now, so I don't see why it cant be added now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants