feat: declarativly toggle visibility #64
Merged
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
visibility (by triggering show/hide) can now be done by declarative angular binding ([isVisible]="true|false")
What is the current behavior?
Now show() and hide() have to be called manually.
Issue Number: #60
What is the new behavior?
Now [isVisible]="true|false" can be used to call show()/hide()
Does this PR introduce a breaking change?
Other information
I tried limit the change to a minimum. Please suggest if something could be done better.