ream88
When mounting my live view, I register it as a participant in a running GenServer.
def mount(_params, _session, socket) do
MyGenServer.add_participant(self())
{:ok, socket}
end
This allows me to easily work with a list of participants very easily. I now introduced some JS dependency which creates a unique ID for each participant/rendered live view and pushes it back to the server, which stores it in its assigns. However for my app to properly work, I would need a list of these unique IDs across all my participants. This can be done via :sys.gen_state, but feels very wrong.
MyGenServer.participants()
|> Enum.map(fn participant →
:sys.gen_state(participant)
|> Map.get(:socket)
|> Map.get(:assigns)
end)
Is there an official way to get assigns from a live-view process from outside of the process?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
benwilson512
I wouldn’t really recommend thinking this way. Assigns belong to the socket. What do you need them for in the genserver?
ream88
I need a way to share the assigns across all my live views. Each live view gets a unique ID, and the other live views connected to the server should see this unique ID. (I need this ID to connect all users to a video channel.)
benwilson512
I would consider using something like Registry so that each live view could register its unique ID.
This sounds like an XY problem. Each live view is a different process, process state isn’t really shareable. You can message it around, but it’s gonna get copied each time and isn’t going to stay up to date as the process state changes. It’s fine to message around the ID, but I wouldn’t do so for the full assigns. Can you elaborate on what you’re trying to do more?