[Accordion] Add expanded value to custom event handler #1689
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
- Add example
dvoituron
requested changes
Mar 14, 2024
dvoituron
approved these changes
Mar 14, 2024
vnbaaij
added a commit
that referenced
this pull request
Mar 15, 2024
* -Fix #1678 by adding expanded value to custom event handler - Add example * Change Expanded type from bool? -> bool
vnbaaij
changed the title
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.
Fixes fix: Set Expanded property to false on FluentAccordionItem from code after manual expand., not working. #1678
The AccordionItem
Expandedparameter is now 2-way bindableAdd example: