afadil
Plugin development workflow hates me and wants me to die
I tried following your plug-in workflow development process. I know Javascript (and plenty of Typescript) for 20 years, but I'm nothing like a professional. Even the setup steps, IDE integration, etc. etc. is far too much, and I've given up on trying to build a simple data plugin for Fidelity UK.
I don't understand why I can't just write a single file, with some kind of hooks exposed like optional functions or similar for the functionality I want to provide. I understand you want people extending the UI, but really the bottom of the barrel value add is in all the little integrations like scrapers for account data etc. that people would happily write, but not if it turns into a whole weekend project.
It goes without saying if this is the first cut of the plugin environment, anything I do work on will be a pain to upgrade later if you choose to change the plugin interface significantly. I don't sling the whole Javascript toolset, and even the thought of a big migration procedure for a massive project puts me off continuing.
Any chance of a lighter weight option? There is huge value in letting folk write scrapers for their own asset price history and potentially custom CSV importers or something like that. But if it requires so much effort to maintain, that's unlikely to happen.
I'd be willing to invest 50-100 LOC in a single file to scrape prices from Fidelity. That I know I could easily maintain and fix up in future too. Any more effort than that and I'm really turned off from trying at all
I'm in the same position. I tried to get the VsCode workflow to work but it fell over because the docker container requires GPU=all which doesn't work on an M series mac so the whole thing falls over. Surely it can run the webserver without requiring architecture specific GPU stuff for plugin development.
I also agree that the design choices make it extremely cumbersome to add even basic features or data into this app, because there is a very thick layer of UI integration at every stage. Despite this, I am trying to climb the learning curve and get something done. @sticilface do you really have to use Docker ? I managed to run with local Node and avoid any virtualization whatsoever.
