Feature: Contact Filtering in Header (Fragment Communication Example) #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey @armand1m , sorry for the delayed response on this. This is awesome! Happy to merge it, but I just switched to yarn to improve the installation experience, so if you want to remove the conflict with |
|
This would close #7, too, I believe. |
|
@tsnolan23 hey! I will solve those later today then =) |
|
Sounds good @armand1m |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What it does
This adds an Example of Fragment Communication, such as asked in #7.
This is a simple Contact Filtering input in the Header, that emits a
CustomEventon each change so the Contacts fragment can listen to that.