Sure, in that case you just namespace the event by the device it came
from. There's an open-source repo here, containing an implementation
for 0.16 -> https://github.com/eeue56/elm-debugger. It should only
really be used for inspiration.
If you need more help implementing it, then Slack is general
On Friday, March 3, 2017 at 10:55:30 AM UTC, Noah Hall wrote:
>
> Like oh-so-many things, I implemented this about 1.5 years ago now. I even
> gave 2 talks on it. With Elm 0.17, you can implement it in under 30 lines
> of code, using firebase as a host. Sadly, the recordings of both the talks
>
Like oh-so-many things, I implemented this about 1.5 years ago now. I even
gave 2 talks on it. With Elm 0.17, you can implement it in under 30 lines
of code, using firebase as a host. Sadly, the recordings of both the talks
I gave on it are lost. But you can read it here ->
https://github.com/eeue5
No but that would be a really cool idea, I can think of several places that
this could be useful, for example checking that things work the same on all
browsers. Or being able to generate a sequence of events from a quickcheck
type thing and play them in a browser.
Zach
ᐧ
On Thu, Mar 2, 2017 at 5
Anyone tried something along these lines:
The state of an application in Elm can be re-built by starting from its
'init' state, then replaying all messages to a given state. This is called
event sourcing.
If I am using some application written in Elm, and I want to share what I
am doing with s
