Ian Lyttle

Closing - if this requires further attention, please let me know.

I think this sounds great!

I have really appreciated the test we have for signals! It has uncovered bugs that I have introduced in my development. When we go to ES6, I fear we won't...

leaving this link to a demo-app here (I deleted it from inst), in hopes of revisiting: https://github.com/vegawidget/vegawidget/tree/b5962adca40de3708d370eccc71b46206fd58641/inst/test-apps/signal

I think the approach should be something like this. In the `vegawidget()` function: - given a `vegaspec_vega_lite`, extract all elements that have a path `usermeta$vegawidget$signals`, combine in a list named...

Another crazy idea that, hopefully, by writing it down here, I will have purged it from my system so that I can do higher-priority "stuff". This, from the [V8 intro](https://cran.r-project.org/web/packages/V8/vignettes/v8_intro.html),...

I have tested this on the infamous [Observable signal-patch demo](https://observablehq.com/@domoritz/rotating-earth) - a duplicate signal-definition (based on name) will throw an error. I can see this being a potential problem in...

Mapping a way forward: - [ ] write up a couple of example specs that use signals (both standard and composed) - [ ] make sure we get the right...

this will have to wait until we have validation sorted, #4

Here, when `validate()` becomes available, we can issue a message if *V8* is not available saying that we did not validate.