What's new in

2.2.2

• fixes issues with deleting

2.2.1

• fixed issue with insert

2.2.0

• removed unhandy intermediate commit: we will do that internally

store.value?.store.entities?.onItemUpdated { [weak self] entry, _ in
    dataProvider.remove(entry)
    //dataProvider.commit() -> don't need to do that anymore, it's too unhandy and doesn't feel like a proper solution
    dataProvider.add(entry)
    dataProvider.commit()
}

• added animation options for dynamic content provider adapter

2.1.0

• added move method of uitableview to recycler view
• instead of committing the UI changes to the tableview, you can now revert them by calling rollback
• fixed: now neighter the content nor the sections will automatically be added before the commit is being called. Unless the commit has not been called, the content of the sections and rows in the sections stay the same
• HINT: if you ever come into the situation where you needed to move the last cell from a section into another and remove the last section, you will have to perform an extra commit() step right after the entry has been removed. This resolves an inconistency in the tableview:

  store.value?.store.entities?.onItemUpdated { [weak self] entry, _ in
      dataProvider.remove(entry)
      dataProvider.commit()
      dataProvider.add(entry)
      dataProvider.commit()
  }
  

2.0.0

• changed reload behaviour, update sections will now be triggered when a commit is being performed

1.12.1

• fix reload bugs

1.12.0

• implement reload of content in section for DynamicContentProviderAdapter

1.11.3

• create further testcases

1.11.2

• create further testcases

1.11.1

• fix NSObject classes couldn't be inferred correctly as Reuseable Types ** added Testcase for this

1.11.0

• provide section sorter, because it is easiert to provide a sorting algorythm than do can calculation the position in the contentSectionizer closure.

contentAdapter.sortSections = { firstSection, secondSection
    guard let first = firstSection.rows.first(where: {firstSection is TimeModel}) as? TimeModel,
        let second = secondSection.rows.first(where: {firstSection is TimeModel}) as? TimeModel else {
            return firstSection.rows.contains(where: { firstSection is TimeModel })
        }
    return first.date > second.date
}

• revert contentSectionizer: you should eighter return .new([String: Any]) or .use ** provide a context within ```.new(...)", this will help you in any further sorting or updating algorithm

• use predicate in section context to decide wheter the content applies to the section. To set the preducate use a dictionary and provide the key Section.Keys.predicate with an NSPredicate Object in the contentSectionizer closure. You can also provide any other key-value pair in that context that you can use within the sectionInitializer and sectionContentUpdate colsures.

let context = [Section.Keys.predicate: NSPredicate(block: { content, _ in
    guard let content = content as? TimeModel else {
        return false
    }
    return content.date > start && content.date < end
}), 
    "Title": "\(calendar.component(.weekOfYear, from: start)) \(calendar.component(.year, from: end))"] as [String : Any]

...

return .new(context)

Now to check wheter a new content meets the predicate of any section, use:

if let index = sections.firstIndex(where: { section in
    return section.meetsPredicate(content: content) ?? false
}) {
    return .use(index)
}
return .new(context)

Be aware: if you provide a predicate for the section, it affects the section.add(row: ...) and section.insert(row: ..., at: index) methods aswell, because they validate if the content meets the predicate.

1.10.0

• provide section sort algorythm in dynamic content provider adapter ** use append, insert() or use() in the section

1.9.1

• fixes where DynamicContentProviderAdapter has not been exposed

1.9.0

• Added .reload(), because you sometimes want to update the recycler view without animations
• You can't access to the header or footer of the section directly anymore. Set the header with section.set(header: ) or the footer with section.set(footer: )

1.8.2

Fix: class models can't be used for dequeuing a cell

1.8.1

Update Gifs

1.8

Remove necessaty of compareable porotocol used for inserting or delete of contents in the section.

1.7

Customize your inserted, reloaded or deleted content with given animations. Can you imagine the struggle to switch between a login or register on the same screen? Or when you want to show or hide a date picker, when tapping on a cell? Now that struggle has been solved. Remove the cell you want to replace and add or insert them at the specific position.

func toggleRegisterOrLogin() {
    section.clear()

    if isLoginPresent {
        isLoginPresent = false

        section.add(row: TextEnterCell.Content(title: "E-Mail", content: email, isSecure: false, delegate: self), animation: .fade)
        section.add(row: TextEnterCell.Content(title: "First name", content: firstName, isSecure: false, delegate: self), animation: .fade)
        section.add(row: TextEnterCell.Content(title: "Last name", content: lastName, isSecure: false, delegate: self), animation: .fade)
        //... any further content that has to be filled
    } else {
        isLoginPresent = true

        section.add(row: TextEnterCell.Content(title: "E-Mail", content: email, isSecure: false, delegate: self), animation: .fade)
        section.add(row: TextEnterCell.Content(title: "Password", content: "", isSecure: true, delegate: self), animation: .fade)
    }    
}

I once was asked, how easy it was to show a text as a cell with this simple library. Now that's pretty easy: In the UITableViewController add following lines to your code:

dataProvider.register(cell: UITableViewCell.self, for: String.self) { cell, content in
    cell.textLabel?.text = content
}

Now add a string to your section:

section.add("Hello World")

We remove pain for you! Have fun(c)!

1.6

Bugfix where the system and custom TableHeaderFooter View have not been displayed: we had to intercept UITableView's delegate, because the viewForHeaderInSection and viewForFooterInSectionis only located in there (?). If you would like to be able to use the delegate without breaking the SwiftDataProviders Section Header and Footer display logic, just assign to the delegate before creating the SwiftDataProvider. It will intercept only the methods that ask for the Header- and Footer View and forward any other delegate callback to your logic

override func viewDidLoad() {
    super.viewDidLoad()

    //do assign to the tableviews delegate ALWAY BEFORE creating and assigning
    //the SwiftDataProvider to the UITableView or UITableViewController, otherwhise
    //the section header and footer view won't appear, when you handle them within the SwiftDataProvider
    self.tableViewDelegate = self 

    self.swiftDataProvider = SwiftDataProvider(recyclerView: self)

    //step 4
}

Added: Register Header Footer view with nibs

    dataProvider.registerHeaderFooter(nib: HeaderView.nib(), as: HeaderView.self, for: HeaderView.HeaderContent.self) { _, _ in 
        // initialize the header view here
    }
}

1.5

So, we reviewed our code and rethought of how we could improve and reduce code and there your are:

1. No need for those Generics in SwiftDataProvider

private var swiftDataProvider: SwiftDataProvider?

2. No need to explicitly set the swiftDataProvider as the dataSource (we do that implicitly)

//tableView.dataSource = swiftDataProvider

3. DEPRECATIONS: Every register(::) methods have now been moved to SwiftDataProvider (due to code simplifying)

If you have any problems with using this classes, please file an issue. I'd be happy with every feedback/codereview!