Migrate search input component to UI-kit
See original GitHub issueIs your feature request related to a problem? Please describe.
The Search input
component that is used in Products Filters is going to be also used in Orders Filters and Customers Filters and could be migrated to the ui-kit from the shared packages folder. (Similar to the SearchSelectInput
).
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Migration - UIkit
Uikit 3 offers a migration tool that runs in your browser and lists all necessary changes from an existing Uikit 2 site. Two...
Read more >@commercetools-uikit/search-select-input - npm
A search select input component built on top of `@commercetools-uikit/async-select-input` to asynchronously load results (options) using the ...
Read more >Interfacing with UIKit — SwiftUI Tutorials - Apple Developer
This tutorial shows you how to convert the featured landmark from the home screen to wrap instances of UIPageViewController and UIPageControl . You'll...
Read more >Migration guide | UIKit React SDK | Sendbird Docs
You can execute key chat functions through various modules provided by UIKit for React. In each module, there is a provider, a set...
Read more >Create a Dynamic Form in UIKit (Compositional ... - YouTube
In this UIKit tutorial, we're going to look at how we can build a scalable dynamic form in UIKit with self sizing UICollectionViewCells...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, yes that was our idea too. We just wanted to get both things moving at the same time 😃
I see, thanks for the info! This will be under discussion and will probably be added to our roadmap.
Meanwhile, perhaps it’s best to move it to shared/experimental on the MC, so you can already use it across the different apps and rework it at will with ease, while trying to keep it consistent with the API of similar ui-kit components so that later it can then be moved seamlessly to the UI-kit with minimal adjustments.