react-testing-library

Describe the feature you'd like:

As far as I understand it, the toHaveDisplayValue matcher takes some kind of input element and computes the value that the user can see.
However, it does not work properly for range widgets (e.g. <input type="range">, but also elements with role="range" or role="slider").

According to the [standard](https://www.w3.org/TR/wai-aria-1.1/#aria-valu

Overview

As the needs of our WhatsApp hotline has declined, we decided to stop operating it. Today is the last day of our hotline volunteers operating it.
Therefore, we need to remove all links going to our WhatsApp Hotline as soon as possible.

I have no complaints about Recoil, I think it is a wonderfully maintained library.
There are two things that concern me, that has requirements include integration with Meta's specific technology the Relay.
And the frequency of Breaking Change is too much.

The existing withErrorHandling should be replaced with react-error-boundary, because it decouples the error state from the widget component (and provides some developer experience features).

• Blog post
• [Testing Error Boundaries](https://testingjavascript.

Context (current result)

Currently the canvas items and code in the Monaco Editor does not save when user closes and quits fflow. This feature was previously implemented using localForage and broke during a merge therefore the partial code is still present in App.jsx and localStorage.js.

Expected result

Canvas items and code persists when user closes and reopens the application.