Board Thread:Watercooler/@comment-3032314-20181119015150/@comment-3032314-20190102232413

Hey, sorry for not getting back to you on this! To answer your question, I still don't have a definitive answer to the CSS problem, though I'm currently strongly leaning toward keeping it inline. I just don't think markup alone is enough to make T usable on Mercury. :(

In the meantime, I've been working on a rewrite of the T parser (which I've been calling "Parsemageddon", haha), to make it more consistent and less dependent on flags. I haven't quite finished that yet, especially because I took a break to work on Dev:Set. One of my concerns about that project though is breaking changes.

I specifically marked T as "unstable" and listed its major version as zero to signal that the API would change eventually. However, I'm worried that other editors saw the documentation and assumed that it was safe to use&mdash;and that, therefore, Parsemageddon will trash a bunch of external wikis. What do you recommend?