Closed ntziolis closed 2 months ago
Run & review this pull request in StackBlitz Codeflow.
@EricPoul can you please review this?
Please let me know if you feel I should add additional unit tests. I added just enough to make them fail (multiple effects in a single provider). And the added a fix and retested.
LGTM
No need for an extra test. Just check that spy3
is called the same number of times as spy1
in the existing tests.
No need for an extra test. Just check that
spy3
is called the same number of times asspy1
in the existing tests.
Done. That said I used spy3 to cover some additional edge cases instead of just mirroring spy1.
Thank you for the fix!
One note. While I would not consider this a breaking change as such, since it just ensures the expected behavior. It does change significantly how the directive functions and might affect existing apps in a way that might not be easy to see for other devs. Not sure what the right way would be to go about this.
It should be fine generally. If someone faces a problem, it's because their code has worked wrong. While it is breaking change in some way, I don't see a problem.
@NetanelBasal I created a tag and updated version but it still isn't available for downloading/ Could you check what I missed?
I need to publish it
Done
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce? Ensures correct behavior of directive when on destroy is called
What is the current behavior?
Only the last (order) effect in a provider was unregistered.
Issue Number: #72
What is the new behavior?
All effects are of a provider are unregistered.
Does this PR introduce a breaking change?
Other information