Jarrad Whitaker

One note on this - most of the validator tests are written more like integration/functional tests, not unit tests - this is fine in general, but it does mean that...

Two approaches - - hand-write custom validation code for Parameters (also Outputs and Metadata and probably others) (not actually that awful, it would be quite small and probably reusable between...

I was wondering about a JS file instead of a JSON file, that way we could just write arbitrary validation functions. (this one is also something I've been wondering about).

probably a) is the best solution :) might be worth doing b) in the interim though.

this is fixed in the latest cfn spec i think

I guess something to do with evdev.py#287 where you only read touch and button events.. this seems intentional because when I loop through all events it works for a second...

I think Plots.jl can already basically do this with the basic `plotly` backend, I'm gonna try and strip it out and create a MWE over PlotlyJS.

Cool so @sglyon I have basic functionality working with only the PlotlyBase package. ```jl import UUIDs function plotly_html_body(plt) uuid = UUIDs.uuid4() html = """ PLOT = document.getElementById('$(uuid)'); require(['https://cdn.plot.ly/plotly-latest.min.js'], function(plotly) {...

> Is there any chance you could consider removing the display_dict override in PlotlyBase.jl? @sglyon ping on this :) I'm happy to submit a PR, just want to check that...

I've been generating a connection string myself because I ran into this and other things.. ```r pii_conn % paste(.data, sep=";", collapse="") ) ``` This has the advantage you can quote...