Closed lencioni closed 7 years ago
I'm definitely pro this, although I don't have the same bandwidth converting diffux as I had for import-js.
That's fair. Me too, unless I am able to do this during the day. I think this conversion may be easier anyway--we certainly have a lot fewer tests to convert.
I'm doing a bit of research on this. I think the biggest open questions for me is what will we replace our dependencies with? Some of them seem like they will have pretty straightforward or obvious replacements (e.g. s3, selenium-webdriver, sinatra (I was thinking express)). So I've been looking into what we might replace chunky PNG and diff-lcs with.
I discovered png-diff which appears to do some of the same things we'll need to do here. This lead me to pngjs for reading and writing PNG files. Seems promising.
adiff might be worth looking at to calculate the diffs, but I'm not sure if it is able to operate on arrays or 2D arrays.
I think that instead of writing out diff PNGs and uploading separate images, we can just generate the diff images in the browser using canvas or something. That will bring us one step closer to everything being in JS.
This is done!
I've been floating this idea around in my mind for a while, and I think it is time to open it up for discussion. Ruby has served this project well, but I think if we want to take it to the next level, we should consider rewriting in JavaScript at some point.
Advantages
diffux.describe
(e.g.import { describe } from 'diffux';
)Disadvantages
Other considerations