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
FYI, noticing that several of the props, (scopesTypeLabel, scopes, selectedScopes, translateWithId, sortItems) are meant to be passed to the MultiSelect. Since these are all related, I wonder if it would make sense to follow the approach from @davidmenendez where we have Dropdown in AddSelect and we group these related props in an object/array.
yeah i agree with this. basically any time that we're working with multiple carbon components we should do our best to enable users to pass as many props to those components for maximum flexibility. unless there's a specific callout in the design to not use something specific we should probably have something like btnProps = {} and multiSelectProps = {}
@jlongshore Do we want to add more migration detail in Box or include details directly in #4437
Yeah If you like you can do your work in the Box note and I can update the migration doc from it... Reviewed the changes, I believe this is everything that a user would care about
Originally posted by @davidmenendez in #4239
Acceptance criteria
The text was updated successfully, but these errors were encountered: