Replies: 1 comment 2 replies
-
Would you be open to hopping on a call to chat about this sometime? The word "plugin" is one of those that might refer to a few very different things and approaches, and there are a few different ways to think about extensibility as well — e.g. whether you're connecting different adapters to each other, or just supporting multiple adapters in the same tool. I'm worried about misinterpreting your questions and accidentally giving you the wrong answers. It's currently possible to compile Rust adapters to WASM and run them that way — that's how the rustdoc query playground works (though it's a bit hacky): https://github.com/obi1kenobi/trustfall/tree/main/experiments/trustfall_rustdoc So I think a solution is likely possible, but it is a question of how to best approach the problem to make the solution future-proof. If you'd be open to hopping on a call, I'd love to chat! What's your schedule like next week? Which days / times would be best? |
Beta Was this translation helpful? Give feedback.
-
So I wrote a tool that allows my team to lint OpenAPI and Terraform here but I want to make it more extensible by making the adapters be WASM plugins (since the ABI is not stable). My concern (lack of knowledge and experience in plugin systems) is how to structure it. So currently, you are only able to pass numbers and strings between the host and the plugin. This is not too bad since we can just serialize the data to a JSON string and pass that. But with the Vertex enum, this might be an issue especially since not all languages will be able to support it.
My other concern is the Adapter/BasicAdapter traits. I am not sure if this translate well across the plugin.
Any ideas, suggestions etc are welcome
Beta Was this translation helpful? Give feedback.
All reactions