lemaster
Currently we have stream_insert and stream that can either add new items to a stream or update existing items if they are already present on the client. It would be good to also have stream_update (or alternatively an update_only: true/false option) that would update an existing stream item if it is present on the client side or ignore the item if it is not already present.
The use case is a bunch of users editing items in a tableview of a potentially large data set. If 2 users can see the same item, it would be nice to show the items updating, but if both users are looking at different portions of the dataset, i don’t want items popping into view just because the other user updated them.
I have some time to help to implement the feature, but I would need someone to walk me through the interaction between the LiveView’s concept of the stream on the server side and client side version of the stream first. Alternatively, if there’s a way to handle this use case with the existing streams api, I’m happy to learn.
Where Next?
Trending in Proposals: Ideas
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
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
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
steffend
Hey @lemaster,
this reminded me of Updating a stream element without inserting · Issue #2690 · phoenixframework/phoenix_live_view · GitHub.
I also opened stream_insert update_only aka stream_update by SteffenDE · Pull Request #3573 · phoenixframework/phoenix_live_view · GitHub, where you can see how this could be implemented. There are no tests yet, because I first wanted to see if José thinks that now’s the right time.
If anyone wonders how to do this in the meantime: you can implement this by keeping a MapSet of rendered ids in your assigns and only
stream_inserting if the ID is in the set.lemaster
Wow, thanks for jumping on this! I think the solution in your PR is much better than maintaining a MapSet on the server. If you are using a limit with the stream, rather than maintaining a MapSet, you would need to maintain a list, and duplicate the logic of the stream yourself. If you mess up there’s a real chance of your stream diverging from your id list.