Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unstable_autotrackMemoize Errors #637

Open
ChrisMart21 opened this issue Nov 13, 2023 · 1 comment
Open

unstable_autotrackMemoize Errors #637

ChrisMart21 opened this issue Nov 13, 2023 · 1 comment

Comments

@ChrisMart21
Copy link

Testing out the unstable export unstable_autotrackMemoize and keep encountering this error message

proxy can't report existing configurable property '0' as non-configurable

Using an imported createSelectorCreator() Instance
export const createAutoTrackSelector = createSelectorCreator(autoTrackMemoize);

It seems to be working fine until it hits the last section of checks in the selector

Replay of the error.
https://app.replay.io/recording/open-energy-dashboard--6f007eb1-1ca2-48da-8dd9-fe05630fc0e7

@markerikson
Copy link
Contributor

First, thank you for taking the time to make a Replay!

...... unfortunately it seems like the recording is broken enough that I can't actually pause anywhere and fully inspect what's happening :( Sadly, our Windows + Firefox version of the Replay recording browser has been pretty flaky for a while, and a lot more unstable than the Mac or Linux versions. And I say that as the lone Windows user at Replay.

The best workaround I've got atm to make a useful recording is to actually manually download our Chromium + Linux build around WSL, make the recording with that, and manually upload it with our CLI. But that's also annoyingly painful right now - we don't yet have the "Record" button in Chrome's UI, so there's several extra steps needed. (We're actually adding that "Record" button right now and hope to have it ready in a few weeks.)

Back to the Reselect side: we're going to end up deferring any further work on unstable_autotrackMemoize past the upcoming Reselect 5.0 major release (which we're targeting for the start of December, along with all the other RTK 2.0-related packages). So, I definitely want to investigate this further, but it'll have to wait until after RTK 2.0 is done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants