Better and more convenient extension development #597

zmh-program · 2023-06-18T00:18:35Z

zmh-program
Jun 18, 2023

I like making turbowarp extensions, and I've made the cloud database extension and the OpenAI extension before.

But I have found a problem, especially when the project gets large, that it can be a bit time consuming to weave between block parameters and functions, and I think this may not be as well designed. In particular, the readability becomes worse at post-maintenance time.

So I'm thinking about how to make the extension interface more reasonable and make extension production easier and more efficient, instead of spending a lot of time or even sacrificing readability because of a configuration.

So I wrote a plugin turbowarp-clipx. at first, although I think it has been able to reduce a lot of time wasted because of the configuration, but I think it is still not worth to promote. Later, I wrote a built-in cache, a better interface style, and I finally figured out how to automate the translation.

Like many front-end projects, the i18n process is tedious and time-consuming, especially when it comes to changes, and

Automated translation cuts the time spent on manual translation the most.

So I made it. In the end, it turned out to be less than a quarter of the total code in many cases, and most importantly, the developer could develop extensions very efficiently, very easily, and with very simple continuous CI/CD, without having to care about shuttling between configurations and methods.
As well as I also developed the function of github workflow to automatically package and publish.

So, how should I do? It's very simple, just use the template, see the project for details :)