fix(module:cascader): add nzClear functionality to cascader #6761
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add the missing nzClear emit to the clearSelection method on the cascader component.
Extend the cascader e2e tests to ensure that the event emitter works as expected.
fix #6751
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The nzClear event emitter would not emit when the cascader value was cleared as the implementation was missing.
Issue Number: #6751
What is the new behavior?
When the clearSelection method is executed on the cascader component, the nzClear event emitter will now emit to inform any cascader component consumers.
Does this PR introduce a breaking change?
Other information
Used .spyOn and .toHaveBeenCalled to test the event emitter in the e2e spec for the cascader file.
Tests are passing.