Renamed to bellroy/elm-eventstream. It is published under that name, and new versions come out there.
Versions published as tricycle/elm-eventstream still install under that name. 2 versions of 3 come from the new location (see their notes). 1 version could not be recovered and cannot be installed.
Rerouted (renamed, needs approval). The GitHub user or repository was renamed. The tag is still there, at the new name. The Lamdera package server serves a copy recovered from https://github.com/bellroy/elm-eventstream.
What we checked: The repo moved to github.com/bellroy/elm-eventstream and tag 1.0.0 is there; its commit 5c531e7837b3 is from 2021-04-07 02:39 UTC, after the version was published (2019-05-20 03:58 UTC); elm.json differs from package.elm-lang.org's; the exposed modules match docs.json; the zip's SHA-1 is not the published one and nothing else confirms its contents.
We could not verify this copy against what was published, so the Lamdera compiler asks before using it (y/n). Without a terminal, as in CI, it stops with an error unless approved:
lamdera make --auto-approve-package-rerouting approves rerouted versions for that run,LAMDERA_AUTO_APPROVE_PACKAGE_REROUTING=1 does the same for every run in that environment,LAMDERA_CACHE=off skips the Lamdera package server altogether: packages come from package.elm-lang.org and GitHub only, as with elm, and a rerouted version then fails to download.Details · package.elm-lang.org's zip: https://github.com/tricycle/elm-eventstream/zipball/1.0.0/
Keep track of a stream of events and set triggers that send out outgoing events.
Currently in use by us to supply the Google Tag Managers Data Layer with safely encoded events.
Create an EventStream
Attempt to add a new event to the EventStream
The minimal expected structure of an event needs to look like;
{ "eventName": "YourEventName",
"eventData": "Data for which you supply a decoder that confirms it's validity and match"
}Get RawIncomingEvents that match query from the eventStream
A structured error describing why your mutation to the EventStream failed. You can use this to give feedback to the developer who might be adding an unknown or misformed event.
Convert an EventStream error into a String that is nice for debugging.
The Matcher is currently an alias for the Core String type.
The Matcher allows for more advanced, event specific triggers to be set.
You might have an event A that contains a field name on which you want to place a specific trigger.
This could then look like A.someValue.
Please refer to the tests included for more examples
The EventStream holds the possible eventNames and matchers, triggers for outgoing events and ofcourse every past events