Without this change we can see a crash in the app because the size for an unknown cell is requested. I think this is caused by the call to performBatchUpdates triggering a layout before the indexes have updated.

This works around a bug from ~iOS 14 that causes the last N items in a section to ignore any updates applied to them when N items are deleted from the same section and the items are at the end of the section.

This also removes the conversion of inserts/removals in to updates, which reduces the need to account for these synthesised updates and also more closely matches the intent of the user; if something has truly moved or been updated the appropriate methods can be used, while removals and inserts that happen to result in the same position will not animate as a refresh.

This also fixes the crash that #6 was originally aiming to fix. It became much easier to reason about the changes once the reloads were not synthesised and were using the post-updates index paths. I think this probably fixes some other bugs. At a minimum the existing tests were updated or still passed, plus new tests have been added.

I also created https://github.com/opennetltd/ComposedUITests/pull/1, which adds some more tests to the integration project. These are mostly used to validate that the unit tests here are correct according to UICollectionView, e.g. it does not crash, request any unexpected cells, or fallback to a reloadData.

This is an improvement but it's not quite a fix yet.

I think the issue is in the transforming of the index paths. We probably need to work with a mixture of the current and the transformed index paths in ChangesReducer.removeElements(at:) but I can't figure out the right mix and need to step away for a bit to clear my head of this, hopefully coming back with "fresh eyes."

I'm hoping this is a clearer API compared to using SelectionHandler.shouldSelect(at:) or SelectionHandler.didSelect(at:).

The primary change here is to enable strict concurrency checks via ~~-Xfrontend -strict-concurrency=complete~~ the StrictConcurrency experimental featyre. The main knock-on effect of this is that @MainActor has been added to most protocols and types.

I also:

• Bumped the Swift tools version to 5.9
  • With this the name parameter on the dependency declaration has been deprecated
  • This initially 5.7 but have since moved on to Xocde 15.1
• Removed support for all but UICollectionViews
  • We don't use any of the other view types so this has no impact on us, other than less to update and maintain
  • We did rely on some of the extensions on UITableView. The PR in the main repo now includes these extensions
• The required initialisers on ArraySection have been removed
  • I planned to remove these soon because they make it harder to subclass, but these have been removed now because they were used for protocol conformances that cannot be satisfied with an actor-isolated function

• Explanation: When assertMacroExpansion fails, it incorrectly displayed the expected source as the expanded source.
• Scope: The assertMacroExpansion test function
• Risk: Very low, only changes the description in case of an XCTFail
• Testing: Tested manually
• Issue: n/a
• Reviewer: @ahoppen on #1917

While using this function I was confused by the error message. I think it should include the actual expansion, not what's expected?

I also renamed the variable to try and make it a little clearer and (assuming this is correct) prevent a mistake like this again. This was done in 3c46da3712dec11e5d485c96b6b7d9d40b7c8f25 so can be easily reverted.