You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2022. It is now read-only.
Any interest in a TypeScript rewrite? The code is a bit of a mess and updating it to modern patterns would clean it up a lot. I've not attempted to compile TS in a gem before but in theory the compiled JS could be generated on publish and committed to git.
The text was updated successfully, but these errors were encountered:
That would absolutely be interesting. I use a lot of TypeScript daily now, and it is so much nicer to work with. Never wrapped my head around writing definition files and similar though.
Something I've toyed with for a while, but never gotten around to, is to simply drop the whole gem shenanigans. It feels like a bit of a mess to bundle JavaScript in a Ruby gem that gets installed. But it might be required/easier in order to get it to work with TinyMCE. I sadly don't use much TinyMCE or Rails these days, so haven't kept up with the recommended practices
I don't do a lot of TinyMCE development but I've got a client that wants some features from time to time.
I'm not all that familiar having TS in a gem but I think for ease of use the compiled JS should probably be committed to git and published with the gem. Users probably shouldn't have to have TS/Node available to use it.
Any interest in a TypeScript rewrite? The code is a bit of a mess and updating it to modern patterns would clean it up a lot. I've not attempted to compile TS in a gem before but in theory the compiled JS could be generated on publish and committed to git.
The text was updated successfully, but these errors were encountered: