Add stack-trace to the selector-memo warning? #2065
infinite-persistence
started this conversation in
General
Replies: 0 comments 2 replies
-
Seems like something we could add, yeah. |
Beta Was this translation helpful? Give feedback.
0 replies
-
opened #2064 - that has a build that it'd be great if you could try 🙂 |
Beta Was this translation helpful? Give feedback.
0 replies
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
-
I really like these warnings, but I don't known which selector the warning is referring to because anonymous functions are being used in the repo I'm working on.
If the stack trace is added (in addition to the existing
selected|selected2|state
), that would point me to the right direction.Thoughts? Or perhaps I'm missing something here?
Beta Was this translation helpful? Give feedback.
All reactions