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.
Function onFinishAll is never called
See original GitHub issueThis is how I’m using it.
<FlipMove className="ui horizontal list" duration={300} onStartAll={this.onStartAll} onFinishAll={this.onFinishAll}>
{this.items}
<FlipMove>
[onStart, onStartAll, onFinish] works as expected. Using version 2.9.1
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Why is my function never called, even though I explicitly call it?
When I run this code, I explicitly try to fail IsThing() , even removing literally everything in it except the return false ....
Read more >Form Provider should allow error handling and scrolling to first ...
onFinishAll (function): gets called when all forms validate successfully upon submission. onFinishFailed (function): gets called when one of ...
Read more >react-flip-move - npm
This function is called with a DOM node as the only argument. It should return an object as specified by the getBoundingClientRect() spec....
Read more >Why isn't my function call not working? - Codecademy
Why isn't my function call not working? I keep getting an error to check syntax but I don't see anything wrong. Can someone...
Read more >Chromedriver quit() method doesn't close all chrome.exe ...
You can put the below in the onFinish all tests method which kills them: String systemType = System.getProperty("os.name").
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’ll take a look at it at the end of the week. might also use it to do some dom cleanup, which hopefully prevents some more edge cases with nodes not being removed
Ok then, closing this issue. It could be a problem with another library stopping propagation of events, but i’m just speculating here. If you manage to reproduce the problem, just reopen it.