Before getting started you’ll definitely want to read about the origination of this package… you can do that here.
All right, now that you’re back, this is the issue we’re going to be tackling today. In the first iteration of the package, only string values were supported as filter conditions. Booleans and numbers require a little extra work to normalize and I didn’t want them to slow down getting the initial version of the package published.
As an extra bonus, I’ll be writing this guide as I work through adding this functionality! You’ll be able to keep track of my thought process the entire time and we’ll be able to pair the work in progress to specific commits in the associated pull request. …
The app I’m working on in my spare time has a need to consume large lists of data, with a key requirement of making it easy to filter the list based on properties of items in the list. Additionally, the list should be searchable to further narrow the results.
Or… how the heck is it even possible that the same exact code fails to pass analysis once it’s extracted into a local package?!
I’m working on a generic flutter widget using the
flutter_bloc package that makes it easier to filter and search a list of data (more on that coming soon, but it will expand on the initial work found here). …