[DOCS] - Clarify FluentSelect SelectedOptionsChanged not triggered with manual options (#3670 and #1207) #3680
+30
−0
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.
Clarify FluentSelect SelectedOptionsChanged not triggered with manual options (#3670 and #1207)
📖 Description
This PR improves the documentation of the
FluentSelect
component by adding a clarification about theSelectedOptionsChanged
event.When using manual options, FluentSelect's internal data structure cannot be reliably updated. Because of that, the
SelectedOptionsChanged
callback will not be triggered.This is a known limitation, and we do not foresee changes to this behavior in the short term.
🎫 Issues
Fixes #3670 and #1207
📑 Test Plan
Updated documentation:
Let me know if you’d like me to include any additional details.
Thanks!