Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
force re-render
See original GitHub issueHi,
Would anyone like to see a force re-render functionality? Similar to my request of non-idemptotent routing.
{force:true} option would make the FlowLayout re-render the template, if we want to re-start onCreated callbacks for some reason.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:29 (1 by maintainers)
Top Results From Across the Web
How and when to force a React component to re-render
In any user or system event, you can call the method this.forceUpdate() , which will cause render() to be called on the component,...
Read more >Can you force a React component to rerender without calling ...
I have found it best to avoid forceUpdate(). One way to force re-render is to add dependency of ...
Read more >How to Force Re-Render a React Component & Should you ...
Class Components provide you a built-in method to trigger a Re-Render. Simply use forceUpdate method to force React to Re-Render the component.
Read more >4 methods to force a re-render in React
1. Re-render component when state changes. Any time a React component state has changed, React has to run the render() method.
Read more >How to force a React component to re-render - Rootstack
The setState() method. If the component already has state then you can update the state to its current value in a simple way:...
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
I used the function “BlazeLayout.reset()” before render template again and it’s work fine.
I’m running into that exact issue. If a user switches from route A to route B, but both employ the same template, onCreate only fires the first time. I was setting up a data context there, but now I’ve got to figure out a different way to do this. A force flag would seem like a good option.