arsduo/elm-rings

Programmatically capture the state of your Elm application as your users use it.

elm-rings's Issues

Elm 0.19 support

Elm 0.19 changes some of the details ElmRings relies on; the library needs to be upgraded.

This will happen once Webpack support is fixed for the new version so that I can upgrade and test against the example (see elm-community/elm-webpack-loader#142).

Pull Elm controls out of the DOM on initialization

One way to reduce the security and UI impacts of having debug mode on (see the caveats section of the readme) is to detach the Elm history controls from the DOM as soon as ElmRings is initialized.

We should still be able to programmatically fire the click event on the Export link, since Elm constructs the history export and attaches it to the DOM separately.

Obviously, this would only apply if the allowDownload option is set to is false.

Add Cypress integration tests for the example

It would be good to have integration tests for the example to make sure future changes to the library don't break things -- jest is not bad, but it can't capture the full interaction with the DOM and with Elm.