You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if using custom children in Cascader, for example to perform search using an async api, there is no way to display results in the popup. In the DropDown component, there is visible and onVisibleChange, to optionally make the component controlled.
In the render method of Cascader.js,, inputProps is composed of otherProps with certain props omitted. These include popupVisible. Would be simple enough to remove popupVisible from the omit, enabling the component to be 'controlled' fully.
Is there a valid reason, why this could not be supported?
What problem does this feature solve?
Currently, if using custom children in Cascader, for example to perform search using an async api, there is no way to display results in the popup. In the
DropDown
component, there isvisible
andonVisibleChange
, to optionally make the component controlled.In the render method of
Cascader.js
,, inputProps is composed ofotherProps
with certain props omitted. These includepopupVisible
. Would be simple enough to removepopupVisible
from theomit
, enabling the component to be 'controlled' fully.Is there a valid reason, why this could not be supported?
What does the proposed API look like?
The text was updated successfully, but these errors were encountered: