Swift: Have Searchbar Search Through Both Sections and Not Combine Them

Swift: Have SearchBar search through both sections and not combine them

Right now you create a single array (filteredArray) and assume you have 1 section when searching.

I would remove that assumption.

Inside your filterContentForSearchText method, create an array of arrays (where each inner array represents a section).

Then update all of your table view data source methods to work with that array of arrays to get the proper values.

First, update your declaration of filteredArray to be an array of arrays.

Now update your table view methods:

func tableView(_ tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
    if !(searchController.isActive && searchController.searchBar.text != "") {
        if section == 0 {
            return followedArray.count
        } else {
            return mainArray.count
        }
    } else {
        return filteredArray[section].count
    }
}

// Number of Sections
func numberOfSections(in tableView: UITableView) -> Int {
    if !(searchController.isActive && searchController.searchBar.text != "") {
        return 2
    } else {
        return filteredArray.count
    }
}

// CellForRowAt indexPath
public func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell {
    let CellIdentifier = "Cell"
    var cell = tableView.dequeueReusableCell(withIdentifier: CellIdentifier) as! CustomCell

    if cell != cell {
        cell = CustomCell(style: UITableViewCellStyle.default, reuseIdentifier: CellIdentifier)
    }

    // Configuring the cell
    var blogObject: Blog

    if !(searchController.isActive && searchController.searchBar.text != "") {
        if indexPath.section == 0 {
            blogObject = followedArray[indexPath.row] 
            cell.populateCell(blogObject, isFollowed: true, indexPath: indexPath, parentView: self)
        } else {
            blogObject = mainArray[indexPath.row] 
            cell.populateCell(blogObject, isFollowed: false, indexPath: indexPath, parentView: self)
        }
    } else {
        blogObject = filteredArray[indexPath.section][indexPath.row] 
        cell.populateCell(blogObject, isFollowed: false, indexPath: indexPath, parentView: self)
    }

    return cell
}

And finally update the filterContentForSearchText method:

func filterContentForSearchText(searchText: String, scope: String = "All") {
    let filteredFollowed = followedArray.filter { Blog in
        let categoryMatch = (scope == "All") || (Blog.blogType == scope)

        return categoryMatch && (Blog.blogName.lowercased().contains(searchText.lowercased()))
    }

    let filteredMain = mainArray.filter { Blog in
        let categoryMatch = (scope == "All") || (Blog.blogType == scope)

        return categoryMatch && (Blog.blogName.lowercased().contains(searchText.lowercased()))
    }

    filteredArray = [ filteredFollowed, filteredMain ]

    myTableView.reloadData()
}

How can I use a searchBar in a TableView with multiple sections?

This approach is not appropriate. Instead of using a flag variable as searching and handling different scenarios, all you need to do is to define only a single array for the entire procedure. In your case your data source array would look like this:

[["uno", "dos", "tres", "cuatro"],["a", "be", "ce", "de", "e", "efe", "ge"],["alpha", "beta", "gamma"],["ichi", "ni", "san", "shi", "go", "roku", "nana", "hachi"]] 

Now, everything is much more easier to handle and implement. For example the switch case in number of rows delegate function will be replaced by:

return dataSource[section].count

What you want to do here is to map two distinct arrays to each other when a search result is tapped. I suggest you to create a class when you have multiple attributes relating to one thing:

struct Item {
var title : String // this is cell's title
var text : String // this is what will be shown on the next view controller when a cell is tapped.
}

Your data source will then look like this:

var dataSource : [[Item]] = [[Item(title: "uno" , text: """
SECTION 1, ROW 0 \n
Esto debe venir de section 1 row 0, y para hacerlo realmente largo es necesario meter un montón de cosas irrelevantes para ver si respeta los espacios y los renglones del textView. Gracias de nada.
""") , Item(title: "dos" , text: """
SECTION 1, ROW 1 \n
Esto debe venir de section 1 row 1. Una vez más es necesario asegurarse de que los márgenes y formatos de texto son respetados. De otro modo habrá que corregirlos. \n
Aquí hay un salto de línea. A ver qué tal sale.
""" ) , Item(title: "tres" , text: """
SECTION 1, ROW 2 \n
Esto debe venir de section 1 row 2. \n \n

OTRO SUBTÍTULO DENTRO DE LA SECCIÓN. \n
Se usarán 2 nuevas líneas cuando haya que añadir algún título o subtítulo dentro del textView. Por cuestiones de estética visual.
""" ), Item(title: "cuatro" , text: """
SECTION 1, ROW 3 \n
Esto debe venir de section 1 row 3
""" )] , [Item(title: "a" , text: """
SECTION 2 ROW 0 \n
Esto debe venir de section 2 row 0. Lorem ipsum dolor sit er elit lamet, consectetaur cillium adipisicing pecu, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Nam liber te conscient to factor tum poen legum odioque civiuda. \n \n \n \n \n \n

Aquí sigue la onda pedorra.
""" ) , Item(title: "be" , text: "Esto debe venir de section 2 row 1" ) , Item(title: "ce" , text: "Esto debe venir de section 2 row 2" ) , Item(title: "de" , text: "Esto debe venir de section 2 row 3" ) , Item(title: "e" , text: "Esto debe venir de section 2 row 4" ) , Item(title: "efe" , text: "Esto debe venir de section 2 row 1" ) , Item(title: "ge" , text: "Esto debe venir de section 2 row 5" )]]

Now in your search delegate functions you need to remove unwanted result from the data source array based on the text or simply reset the array to defaults when cancel button is tapped. Once you've done that, all you need to do is to just reload table view:

func searchBar(_ searchBar: UISearchBar, textDidChange searchText: String) {
    self.dataSource = values
    var filteredDataSource : [[Item]] = []
    for items in dataSource {
        let filteredItems = items.filter { (item) -> Bool in
            if item.title.lowercased().prefix(searchText.count) == searchText.lowercased() {
                return true
            }
            return false
        }
        filteredDataSource.append(filteredItems)
    }
    self.dataSource = filteredDataSource
    tableView.reloadData()

}

func searchBarCancelButtonClicked(_ searchBar: UISearchBar) {
    self.dataSource = values //reseting data source to defaults
    tableView.reloadData()
}

And when you select a row, you pass the section and row number incorrectly in your code. In order to pass corresponding data to the next view controller appropriately, you need to do this in your prepare for segue function:

override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
    //assuming your next view controller class's name is ViewController.
    guard let detailViewController = segue.destination as? ViewController,
        let row = tableView.indexPathForSelectedRow?.row,
        let section = tableView.indexPathForSelectedRow?.section
        else {
            return
    }
    detailViewController.item = dataSource[section][row] //passing selected item object.
}

Finally, in your next view controller you have the item object which has both title and text properties. In your case you want to display its text property.
Hope this helps you!

EDIT

Complete solution on github.

How do I combine both searching and filtering tableViewCells in the same viewController?

You can create different filter functions for each search/filter criteria and then apply them using an array and filter

typealias ProductFilter = (Product) -> Bool
var searchKey: String! //just for this example
var newDate: Date! //just for this example, not sure what New filter means

let nameFilter: ProductFilter = { $0.name.lowercased().contains(searchKey) }
let stockFilter: ProductFilter = { $0.stock > 0 }
let discontinuedFilter: ProductFilter = { $0.discontinued }
let newFilter: ProductFilter = {$0.date > newDate}

and then applying the filter using the search key

let filterArray = [nameFilter, stockFilter]

searchKey = "app"
let filtered = products.filter { product in
    filterArray.first(where: {!$0(product)}) == nil
}

UISearchBar not working with sub sections in array

filteredSections is an array of Strings and you are trying to assign the output of a filter function called on an array of Sections, which return an array of Sections, so it obviously won't work.

If you want to return Strings as a result of filtering the array of Sections, you need to combine filter and map, which can be done with a single flatMap.

The ternary operator inside the flatMap checks the same condition as your filter did, but it returns section.subSec.name if the condition evaluates to true and nil otherwise, which the flatMap simply ignores, hence the output array will only contain the matching subsection names.

func filterContentForSearchText(_ searchText: String, scope: String = "All") {
  filtered = sections.flatMap{ return $0.subSec.name.lowercased().contains(searchText.lowercased()) ? searchText : nil }

  tableView.reloadData()
}

Since you didn't include the definition of Section in your code, I couldn't test the function, but if subSec.name is a String, it will work just fine.

TableView search in Swift

I'm working through the same thing today and found this tutorial very easy to follow: https://github.com/codepath/ios_guides/wiki/Search-Bar-Guide

It will take you through the steps of adding the search bar in Interface Builder, setting up the delegate, and including a method to filter the results.

---

Providing a way for users to search through a collection of items is a fairly common task in iOS projects. A standard interface for implementing search behaviors is the search bar.

There are a few common ways to work with Search Bars:

• Directly using a UISearchBar. This is the most bare bones way to use
  UISearchBars. This can be extremely flexible if you want to design
  and program your own search interface, however does not provide as
  many built-in features as the other methods.

• Using a UISearchDisplayController to help manage a search interface.
  The UISearchDisplayController allows you to present a standard search
  interface with built-in animations. This method forces you to display
  search results in a table view. - DEPRECATED

• Using a UISearchController to help manage a search interface. The
  
  UISearchController is a newer controller (available only in iOS 8+)
  
  that helps you present a search interface using any kind of view to
  
  display the search results.

This guide covers the very basics of working with each of these classes. None of these classes actually implements the "searching" behavior of finding items that match a given query string, since determining which objects match will vary with the domain specific use case (e.g. when searching for "people" you might want to match on just their names, whereas you may want a full-text pre-indexed search when searching through e-mails). You'll have to implement any search/filtering behavior yourself.

Working with UISearchBars directly

At its core, a search bar is nothing more than a glorified text field packaged with a scope control and some animations and a couple of buttons. Each search bar has a delegate that gives you an opportunity to respond to user actions. The most important delegate methods are:

• textDidChange - most of the time you'll respond to this event by
  updating the displayed set of search results as the user is typing
  out a query
• searchBarSearchButtonClicked - in some cases if the search operation
  is slow (e.g. requires making a slow API call) you'll want to wait
  until the user taps the search button before updating the search
  results.

Example searching a table

We start out with a single view application with a basic UITableView. You can add a UISearchBar as you would with any other control by dragging one to your view controller in interface builder or by programmatically adding it.

The delegate property of search bar must be set to an object that implements UISearchBarDelegate. Typically you make your view controller implement UISearchBarDelegate and set searchBar.delegate = self in viewDidLoad method.

The code to implement the search behavior is as follows. We maintain an additional array filteredData to represent rows of data that match our search text. When the search text changes we update filteredData and reload our table.

class ViewController: UIViewController, UITableViewDataSource, UISearchBarDelegate {
    @IBOutlet weak var tableView: UITableView!
    @IBOutlet weak var searchBar: UISearchBar!

let data = ["New York, NY", "Los Angeles, CA", "Chicago, IL", "Houston, TX",
    "Philadelphia, PA", "Phoenix, AZ", "San Diego, CA", "San Antonio, TX",
    "Dallas, TX", "Detroit, MI", "San Jose, CA", "Indianapolis, IN",
    "Jacksonville, FL", "San Francisco, CA", "Columbus, OH", "Austin, TX",
    "Memphis, TN", "Baltimore, MD", "Charlotte, ND", "Fort Worth, TX"]

var filteredData: [String]!

override func viewDidLoad() {
    super.viewDidLoad()
    tableView.dataSource = self
    searchBar.delegate = self
    filteredData = data
}

func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell {
    let cell = tableView.dequeueReusableCell(withIdentifier: "TableCell", for: indexPath) as UITableViewCell
    cell.textLabel?.text = filteredData[indexPath.row]
    return cell
}

func tableView(_ tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
    return filteredData.count
}

// This method updates filteredData based on the text in the Search Box
func searchBar(_ searchBar: UISearchBar, textDidChange searchText: String) {
    // When there is no text, filteredData is the same as the original data
    // When user has entered text into the search box
    // Use the filter method to iterate over all items in the data array
    // For each item, return true if the item should be included and false if the
    // item should NOT be included
    filteredData = searchText.isEmpty ? data : data.filter({(dataString: String) -> Bool in
        // If dataItem matches the searchText, return true to include it
        return dataString.range(of: searchText, options: .caseInsensitive) != nil
    })

    tableView.reloadData()
}
}

Here's what this looks like when running. Notice that the search results are displayed in the same table, and there is no presentation of a separate search interface.

Example searching a collection view

Since the UISearchBar is quite simple, it can be combined with any abitrary view to build your own search interface. Here's what it might look like paired with a collection view.

The code for this is essentially the same as in the case with table views.

Cancelling out of Search and hiding keyboard

Once user taps on search bar, the keyboard will appear, and you will notice that it won't go away when you tap on X. You can show Cancel button when user taps on search bar, and when user taps on Cancel, hide the keyboard.

There is a nifty searchBarTextDidBeginEditing method for UISearchBarDelegate that gets called when user starts editing search text. You can show Cancel button in that method:

func searchBarTextDidBeginEditing(_ searchBar: UISearchBar) {
        self.searchBar.showsCancelButton = true
}

When user taps on cancel button, delegate's searchBarCancelButtonClicked method gets called. At this point, you can hide the Cancel button, clear existing text in search bar and hide the keyboard like this:

func searchBarCancelButtonClicked(_ searchBar: UISearchBar) {
        searchBar.showsCancelButton = false
        searchBar.text = ""
        searchBar.resignFirstResponder()
}

Using UISearchControllers (iOS 8+)

A newer way to manage the presentation of a search interface (only available in iOS 8 and above) is via the UISearchController. This controller handles some of the logic and animation of presenting a separate search interface for you while still allowing you to specify how your search results are displayed.

Example searching a table

There is currently no built-in object in the Interface Builder Object Library for a UISearchController. The easiest way to create one is to do it programatically. This also creates a UISearchBar and sets the search controller's searchBar property to it. You can add this search bar to your view hierarchy programatically.

In order to update your search results you'll have to implement the UISearchResultsUpdating protocol and set the search controller's searchResultsUpdater property.

You don't need to implement the UISearchControllerDelegate unless you need to hook into the events around the presentation of the search interface.

Putting it all together the code looks like this. Notice that we have to read the search text from the search bar in updateSearchResultsForSearchController. One other thing to note is that we set this view controller's definesPresentationContext property to true. This means that the search controller should use this view controller's frame (as oppposed to the root view controller) when presenting the search interface. In this case it means that the search interface will expand above the carrier bar.

class ViewController: UIViewController, UITableViewDataSource, UISearchResultsUpdating {
    @IBOutlet weak var tableView: UITableView!

let data = ["New York, NY", "Los Angeles, CA", "Chicago, IL", "Houston, TX",
    "Philadelphia, PA", "Phoenix, AZ", "San Diego, CA", "San Antonio, TX",
    "Dallas, TX", "Detroit, MI", "San Jose, CA", "Indianapolis, IN",
    "Jacksonville, FL", "San Francisco, CA", "Columbus, OH", "Austin, TX",
    "Memphis, TN", "Baltimore, MD", "Charlotte, ND", "Fort Worth, TX"]

var filteredData: [String]!

var searchController: UISearchController!

override func viewDidLoad() {
    super.viewDidLoad()

    tableView.dataSource = self
    filteredData = data

    // Initializing with searchResultsController set to nil means that
    // searchController will use this view controller to display the search results
    searchController = UISearchController(searchResultsController: nil)
    searchController.searchResultsUpdater = self

    // If we are using this same view controller to present the results
    // dimming it out wouldn't make sense. Should probably only set
    // this to yes if using another controller to display the search results.
    searchController.dimsBackgroundDuringPresentation = false

    searchController.searchBar.sizeToFit()
    tableView.tableHeaderView = searchController.searchBar

    // Sets this view controller as presenting view controller for the search interface
    definesPresentationContext = true
}

func tableView(tableView: UITableView, cellForRowAtIndexPath indexPath: NSIndexPath) -> UITableViewCell {
    let cell = tableView.dequeueReusableCellWithIdentifier("TableCell") as UITableViewCell
    cell.textLabel?.text = filteredData[indexPath.row]
    return cell
}

func tableView(tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
    return filteredData.count
}

func updateSearchResultsForSearchController(searchController: UISearchController) {
    if let searchText = searchController.searchBar.text {
        filteredData = searchText.isEmpty ? data : data.filter({(dataString: String) -> Bool in
            return dataString.rangeOfString(searchText, options: .CaseInsensitiveSearch) != nil
        })

        tableView.reloadData()
    }
}
}

Here's what this looks like when running. Notice that unlike in the search display controller example, we are using the same table view to display the search results instead of overlaying of a separate table view. However, unlike when working with just the search bar, we still have the built in animation when transitioning to the search interface.

Also, you get the logic to show Cancel button and hide keyboard when user taps on cancel button for free when you use this.

Example searching a collection view

We can just as easily use the search controller to search a collection view in place. We still have the presentation of a search interface, but unlike when working with the search display controller we are not restricted to using a table view to display the search results.

The code for this is almost the same as when searching the the table view above. The only notable difference is that we had to introduce a placeholder view in interface builder for the search bar since there are still some quirks with placing a search controller's search bar inside a collection view's supplementary view.

class ViewController: UIViewController, UICollectionViewDataSource, UISearchResultsUpdating {
    @IBOutlet weak var collectionView: UICollectionView!
    @IBOutlet weak var searchBarPlaceholder: UIView!
    ...
    override func viewDidLoad() {
        ...
        searchController.searchBar.sizeToFit()
        searchBarPlaceholder.addSubview(searchController.searchBar)
        automaticallyAdjustsScrollViewInsets = false
        definesPresentationContext = true
    }

    ...
}

Search Bar in Navigation View

A common requirement is to place the search bar inside the navigation bar.

This can be configured programatically in your view controller's viewDidLoad as follows.

When working directly with a search bar:

// create the search bar programatically since you won't be
// able to drag one onto the navigation bar
searchBar = UISearchBar()
searchBar.sizeToFit()

// the UIViewController comes with a navigationItem property
// this will automatically be initialized for you if when the
// view controller is added to a navigation controller's stack
// you just need to set the titleView to be the search bar
navigationItem.titleView = searchBar

Using a search display controller:

searchDisplayController?.displaysSearchBarInNavigationBar = true

Using a search controller:

searchController.searchBar.sizeToFit()
navigationItem.titleView = searchController.searchBar

// By default the navigation bar hides when presenting the
// search interface.  Obviously we don't want this to happen if
// our search bar is inside the navigation bar.
searchController.hidesNavigationBarDuringPresentation = false

UISearchController search bar overlap first cell when active

This is how I set up the search bar and things in viewDidLoad (copied from some of apple's examples).

It presents the found results in the same view controller as your unfiltered data is shown. It also has its search bar in the table header that is hidden until it is needed.

self.searchController = [[UISearchController alloc] initWithSearchResultsController:nil];
self.searchController.searchResultsUpdater = self;
self.tableView.tableHeaderView = self.searchController.searchBar;
[self.searchController.searchBar sizeToFit];

// we want to be the delegate for our filtered table so didSelectRowAtIndexPath is called for both tables
self.searchController.delegate = self;
self.searchController.dimsBackgroundDuringPresentation = NO; // default is YES
self.searchController.searchBar.delegate = self; // so we can monitor text changes + others

// Search is now just presenting a view controller. As such, the normal view controller
// presentation semantics apply. Namely, that presentation will walk up the view controller
// hierarchy until it finds the root view controller or one that defines a presentation context.
//
self.definesPresentationContext = YES;  // know where you want UISearchController to be displayed

// Hides search bar initially. When the user pulls down on the list, the search bar is revealed.
[self.tableView setContentOffset:CGPointMake(0, self.searchController.searchBar.frame.size.height)];

UIKit SearchBar Filter Two Arrays in textDidChange

You better have a model

struct Item {
  let color:String
  let number:Int
}

Then

var all = [Item(color:"Blue",number:11),.....]
var coloursFiltered = [Item]()

And filter it instead

coloursFiltered = all.filter({ item -> Bool in
  if searchText.isEmpty { return true }
     return item.color.lowercased().contains(searchText.lowercased())
  })
tableView.reloadData()

---

func tableView(_ tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
        return coloursFiltered.count
} 
func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell { 
    self.tableView.register(UINib(nibName: "ItemTableViewCell", bundle: nil), forCellReuseIdentifier: "ItemTableViewCell") 
    let cell = self.tableView.dequeueReusableCell(withIdentifier: "ItemTableViewCell", for: indexPath) as! ItemTableViewCell
    let item = coloursFiltered[indexPath.row]
    cell.name.text = item.color
    cell.code.text = "\(item.number)"  
    return cell
}

Swift SearchBar Filtering & Updating Multiple Arrays

If arr1[] and arr2[] are two columns of a single row of data, then you should have a single array. There are many ways of doing this - tuples, classes, structs - but I tend to go for a struct. If you have additional processing that you will want to perform it could be better implemented as a class, but the same principle applies.

Define the struct you need

struct MyDataStruct
{
    var label1 : String = ""
    var label2 : String = ""
}

Then define an array of this type (instead of arr1, arr2)

var myData = [MyDataStruct]()

Then build up the data and search array just as you were before - but into this single structure

myData.append(MyDataStruct(label1: "Hello", label2: "World"))

Final step is in the tableView methods

override func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> xxTableViewCell {
    let cell = tableView.dequeueReusableCell(withIdentifier: "xxCell", for: indexPath) as! xxTableViewCell

    if(searchActive){
        cell.label1.text = filtered[indexPath.row].label1
    } else {
        cell.label1.text = myData[indexPath.row].label1
        cell.label2.text = myData[indexPath.row].label2 
    }
    return cell
}

---

Related Topics