Escape HTML entities in ansi stream about ansi-to-html

[rburns]

That seems like a good idea. Is it something you'd expect to be more involved than running an htmlentities() function over all the text input? Do you think it should be optional (defualt enabled?, disabled?) or always on?

[mmmries]

@rburns I am a total node newb so feel free to tell me what I am getting wrong here.

I don't see any sort of built-in html escaping stuff in javascript, so I looked through the packages on npm and entities looks like the most popular choice or doing html/xml encoding.

I think for a first pass of this feature it should be off by default and can be turned on by passing a flag like:

AnsiConverter = require 'ansi-to-html'
converter = new AnsiConverter({escapeHtml: true})
converter.toHtml(ansiString)

That way we don't change the existing behavior immediately, and then maybe on the next major release we can switch it to be on by default.

Thoughts?

[rburns]

yeah, I think that sounds about right. I can look into implementing it in the coming days. If you get to it first, that's ok too.

[rburns]

fixed with #7