Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feat: Client should not differentiate between wasm and plugin #1147

Closed
cbrzn opened this issue Aug 16, 2022 · 2 comments
Closed

Feat: Client should not differentiate between wasm and plugin #1147

cbrzn opened this issue Aug 16, 2022 · 2 comments
Milestone
origin-qa

Comments

@cbrzn
Copy link
Contributor

cbrzn commented Aug 16, 2022

Now that plugins have the getManifest method defined (when #1046 is merged), the client doesn't need to know if it is interacting with a plugin wrapper or a wasm wrapper
@cbrzn cbrzn added this to the origin-qa milestone Aug 16, 2022
@dOrgJelli
Copy link
Contributor

Is this solved @cbrzn ?

@cbrzn
Copy link
Contributor Author

cbrzn commented Nov 1, 2022

yah @dOrgJelli

@cbrzn cbrzn closed this as completed Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
origin-qa
Development

No branches or pull requests
2 participants
@dOrgJelli @cbrzn