Hi,
The benefits I see are:
1) the big file (~2500 lines) would be split into several modules. This
could be achieved without switching to TypeScript
2) with TypeScript the code will be type-safer than now. This also helps
for better documentation of the expected parameters (e.g. the Ajax
attributes) but only if one can read TypeScript signatures, e.g. mapOfMaps:
{[key: string]: {[innerKey: string]: string}} - this is Map<String,
Map<String, String>>
The drawback as I already said is the eventual problems with sourcemaps.
On Fri, May 17, 2019 at 1:31 PM Sven Meier <[email protected]> wrote:
> Hi,
>
> as one of the few maintainers of that code I'm not in favor of this:
> IMHO it is not worth to introduce a new language and to complicate the
> build process just to generate ~2500 lines of JS code. Code which is
> closely tied to the browser, pretty stable, thoroughly tested and *almost
> never seen much less touched by anyone else than the committers*.
> I really appreciate the work you have put into this, but I don't see any
> advantage. I'd rather reduce and improve the current code in JavaScript.
>
> I don't want to be a spoilsport, but on an official vote to switch to
> TypeScript I will give a -0 at best.
>
> Regards
> Sven
>
>
> --
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
