|
|
|
|
|
|
by narush
1489 days ago
|
|
|
Yeah, we've thought a bit about a plugin API - for the reasons you say, I think it would be an awesome feature to open up to teams! Any tips on going about it? No need to share the secret sauce, unless you want :P To be totally honest, we're not architected super well to support plugins currently. The big challenge would be allowing users to specify this plugin in pure Python (seems like we want this) - but we think that hand-coded UIs outperform autogenerated ones for now. We've been thinking about how to do better though... maybe soon. Of course, if Mito is missing features, we're open source [1] -- all contributions are welcome! Also feel free to open an issue and we can discuss :) [1] https://github.com/mito-ds/monorepo |
|
|
To be honest, we regularly refactor our architecture at bamboolib in order to make sure that there is almost no gap between what we would love to say in natural language and the code that we need to write.
This resulted in a very stable and clear internal API surface (read architecture). So, literally, all we had to do was adding mount points where users could register their plugins and then include those at render time.
The next day, customers could write plugins just as we did. And, as a matter of fact, all the bamboolib transformations, visualizations, views, etc are just sophisticated plugins that our customers could write themselves because they have access to the same API as we do.
So, no secret sauce except for "good architecture" which is easiest achieved as an ongoing effort rather than an one-off project.