fix(effects-directive): unregister all effects of a provider

[ntziolis]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngneat/effects/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?
Ensures correct behavior of directive when on destroy is called

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

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?

[ ] Yes
[x] No

Other information

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[NetanelBasal]

@EricPoul can you please review this?

[ntziolis]

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.

[EricPoul]

LGTM

No need for an extra test. Just check that spy3 is called the same number of times as spy1 in the existing tests.

[ntziolis]

No need for an extra test. Just check that spy3 is called the same number of times as spy1 in the existing tests.

Done. That said I used spy3 to cover some additional edge cases instead of just mirroring spy1.

[EricPoul]

Thank you for the fix!

[ntziolis]

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.

[EricPoul]

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.

[EricPoul]

@NetanelBasal I created a tag and updated version but it still isn't available for downloading/ Could you check what I missed?

[NetanelBasal]

I need to publish it

[NetanelBasal]

Done