getReact function doesn't return latest props
See original GitHub issueHello,
we’re facing a similar issue to the one fixed last week: https://github.com/DevExpress/testcafe-react-selectors/issues/71
so now we don’t get latest props by getReact function after executing some code within ClientFunction
which in turn triggers some props to change in application. And everything gets updated in the UI, but getReact returns incorrect values. And this is very consistent, no amount of waiting helps.
Have any suggestions regarding this? if you need some POC to investigate it, let me know.
Issue Analytics
- State:
- Created 6 years ago
- Comments:16
Top Results From Across the Web
Using a function to return a prop is not returning the prop
The method is working fine and I can return a correct result to the console. However when I inspect my component with react...
Read more >Dealing With Stale Props and States in React's Functional ...
React's useState docs tell us that React will bail out of a re-render if the new state is identical to the previous one....
Read more >Render Props - React
A component with a render prop takes a function that returns a React element and calls it instead of implementing its own render...
Read more >Components and Props - React
Props are Read-Only Such functions are called “pure” because they do not attempt to change their inputs, and always return the same result...
Read more >React.Component
shouldComponentUpdate() is invoked before rendering when new props or state are being received. Defaults to true . This method is not called for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, this is a bug. Thank you for reporting it. I’ll fix it soon.
You’re always welcome!