search

lukbukkit / chartist-plugin-tooltip

Tooltip plugin for Chartist.js
MIT License
16 stars 13 forks source link

migrate project to Typescript and use Chartist v1 API #22

Closed stklcode closed 1 year ago

stklcode commented 1 year ago

+++ WORK IN PROGRESS +++

stklcode commented 1 year ago

Sorry, actually wanted to target my own fork and not yours.

lukbukkit commented 1 year ago

No worries. You're also welcome to create a pull request for all the outstanding changes. The alternative idea is to move this project to a GitHub organization where we can both accept pull requests and publish new versions under a common npm organization. It would be nice if we could find a solution so that we keep a single package on npm updated. A few years ago, I used this plugin in production, but this has changed, and therefore, the project has been running more or less on life-support since then (with a lot of other stuff going on in my life right now). There are also some React charting libraries which are way easier to use than Chartist; therefore, I only invested limited resources in this project. But if you've got a use case for this plugin and the resources to modernize it, that's fantastic to see.

stklcode commented 1 year ago

I have two use cases for Chartist, both utilizing the tooltip plugin. Main reasons here are it's lightweight fingerprint and simplicity to use.

I'm no frontend dev by definition, so likely I won't spent that much time into the project either. However, I have done some major refactoring in the last days, complete TypeScript migration, transformation into a module and more updates targeting Chartist v1 compatibility. The state is close to releasable now. See https://github.com/stklcode/chartist-plugin-tooltip/tree/main

I've done some rebranding to publish it onto a private registry. But not sure, if I really want to publish the project to a public registry for the reasons above.

If you want to, I can create a PR without the rebranding, so it's one project again. There are about 20 forks or at least similar named projects on NPM, a 21. is probably not what we want.

A shared repo with automatic deployment action, e.g. via Github Actions on tagging would be great for maintaining a single product. Could be your fork, could be a single repository.