nmk
Hi everyone!
I am running into a problem writing a test for resetting a stream in an event. I expect that resetting a stream would remove the previously inserted elements, but it seems that it does not.
It works fine when manually testing in the browser, so this seems to be an issue with my test itself or with LiveViewTest.
I wrote a failing test here: Demonstrate stream reset on patch · phoenixframework/phoenix_live_view@98f0568 · GitHub
Does anyone have an idea what the problem might be?
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
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
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
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
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
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
- #metaprogramming
- #hex
- #security











Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
endoooo
I’m running into the same problem testing some filters in a list backed by
stream/4. did you manage to solve your issue @nmk ?I will skip this test for now and subscribe to this topic (and, if I find a solution, I’ll come back here to share
)
nmk
This is not completely resolved AFAIK. I write a fix for the original bug I encountered - Fix stream reset when patching by nmk · Pull Request #2656 · phoenixframework/phoenix_live_view · GitHub - which was merged to master and found its way to subsequent releases.
A few days later I ran into a similar situation and compressed it into a yet another reproduction which was failing at the time at least: Stream is not reset in handle_params on patch · Issue #2629 · phoenixframework/phoenix_live_view · GitHub
Unfortunately I have not had time to look into this in more detail.
I think there aren’t many people testing LiveView (streams) outside of e2e tests involving a real browser. If I have understood the code correctly, the Elixir test client has to emulate quite a lot of what the JS part of LiveView does. It is inevitable that the two implementations would drift apart sometimes. That is why in this case we have failing tests for code which works as intended in the browser.