add quilljs, create channel for syncing documents
This commit is contained in:
28
lib/poex_web/channels/pad_channel.ex
Normal file
28
lib/poex_web/channels/pad_channel.ex
Normal file
@@ -0,0 +1,28 @@
|
||||
defmodule PoexWeb.PadChannel do
|
||||
use Phoenix.Channel
|
||||
alias Poex.Pads.DocumentServer
|
||||
|
||||
@moduledoc """
|
||||
Channel for users of pad documents
|
||||
"""
|
||||
|
||||
def join("pad:lobby", _message, socket) do
|
||||
{:ok, socket}
|
||||
end
|
||||
|
||||
def join("pad:" <> document_id, _params, socket) do
|
||||
contents = DocumentServer.get_contents(document_id)
|
||||
|
||||
{:ok, %{uuid: socket.assigns.uuid, contents: contents},
|
||||
assign(socket, :document_id, document_id)}
|
||||
end
|
||||
|
||||
def handle_in("update", %{"change" => change, "client_id" => client_id}, socket) do
|
||||
DocumentServer.update(socket.assigns.document_id, %{
|
||||
"change" => change,
|
||||
"client_id" => client_id
|
||||
})
|
||||
|
||||
{:noreply, socket}
|
||||
end
|
||||
end
|
52
lib/poex_web/channels/user_socket.ex
Normal file
52
lib/poex_web/channels/user_socket.ex
Normal file
@@ -0,0 +1,52 @@
|
||||
defmodule PoexWeb.UserSocket do
|
||||
alias Ecto.UUID
|
||||
use Phoenix.Socket
|
||||
|
||||
# A Socket handler
|
||||
#
|
||||
# It's possible to control the websocket connection and
|
||||
# assign values that can be accessed by your channel topics.
|
||||
|
||||
## Channels
|
||||
channel "pad:*", PoexWeb.PadChannel
|
||||
#
|
||||
# To create a channel file, use the mix task:
|
||||
#
|
||||
# mix phx.gen.channel Room
|
||||
#
|
||||
# See the [`Channels guide`](https://hexdocs.pm/phoenix/channels.html)
|
||||
# for further details.
|
||||
|
||||
# Socket params are passed from the client and can
|
||||
# be used to verify and authenticate a user. After
|
||||
# verification, you can put default assigns into
|
||||
# the socket that will be set for all channels, ie
|
||||
#
|
||||
# {:ok, assign(socket, :user_id, verified_user_id)}
|
||||
#
|
||||
# To deny connection, return `:error` or `{:error, term}`. To control the
|
||||
# response the client receives in that case, [define an error handler in the
|
||||
# websocket
|
||||
# configuration](https://hexdocs.pm/phoenix/Phoenix.Endpoint.html#socket/3-websocket-configuration).
|
||||
#
|
||||
# See `Phoenix.Token` documentation for examples in
|
||||
# performing token verification on connect.
|
||||
@impl true
|
||||
def connect(_params, socket, _connect_info) do
|
||||
uuid = UUID.generate()
|
||||
{:ok, assign(socket, :uuid, uuid)}
|
||||
end
|
||||
|
||||
# Socket id's are topics that allow you to identify all sockets for a given user:
|
||||
#
|
||||
# def id(socket), do: "user_socket:#{socket.assigns.user_id}"
|
||||
#
|
||||
# Would allow you to broadcast a "disconnect" event and terminate
|
||||
# all active sockets and channels for a given user:
|
||||
#
|
||||
# Elixir.PoexWeb.Endpoint.broadcast("user_socket:#{user.id}", "disconnect", %{})
|
||||
#
|
||||
# Returning `nil` makes this socket anonymous.
|
||||
@impl true
|
||||
def id(_socket), do: nil
|
||||
end
|
Reference in New Issue
Block a user