eeue56 / elm-phoenix

Phoenix helpers for Elm

elm-phoenix

Phoenix helpers for Elm

Channels

The modules under Phoenix.Channel are designed for working with websockets, which Phoenix calls channels. Channels are pretty similiar to Socket.io's namespacing for rooms and events. elm-blogger contains example usage!

elm-phoenix's Issues

Constrained to implicit message schema

Any schema outside of %{status: <status>, response: %{reason: <reason>}} is ignored.

The sample app at https://github.com/NoRedInk/elm-blogger sends down {"topic":"editor:other","ref":null,"payload":{"status":"ok","response":"hello"},"event":"new_msg"} and in Elm this is parsed as { topic = "editor:other", ref = -1, payload = { status = "ok", response = { reason = "NULL" } }, event = "new_msg" }

We should allow a more open schema. We shouldn't have to change the schema Phoenix sends down to use elm-phoenix.

socket_events is never cleared out in model

Socket events is never cleared out in the model which means that anything beyond a short lived accessory is going to bloat out of control. We need some mechanism to clear the socket events.