Changelog History
-
v5.1.1 Changes
February 24, 2019Thanks @NerdBird for pointing out this issue!
-
v5.1.0
October 17, 2018 -
v5.0.0
August 06, 2018 -
v4.0.0 Changes
September 19, 2016👍 Not too much of an overhaul. However, in order to support Swift 3.0, there were a couple of changes that needed to be made.
- ⚠ First off, the use of PrediKit in Swift 3 caused a bunch of unused result warnings. This has been fixed by assigning the
@discardableResultattribute to any function that returned aFinalizableIncluder<T>. This change shouldn't affect anything you are already doing. - ⚠ One breaking change is to variables that returned a
FinalizableIncluder<T>instance. These needed to be converted to functions since you can't mark variables with attributes. The unused result warnings wouldn't go away until I converted these variables to functions so I can mark them with@discardableResultattribute.
If your code uses these variables (for example, the use of
includeIf.string(property).isEmpty), then you need to add an open and close paren to the end of the variable.This means that current use of these variables will be returning a
() -> FinalizableIncluder<T>function pointer instead of the result of the function. This may result in errors that look like this: "Binary operator '&&' cannot be applied to operands of type 'FinalizedIncluder' and '() -> FinalizedIncluder'". The fix is to simply tack on a()to the end of the closure operand value.- Another breaking change is the change of all includers to use
Stringsinstead ofSelectors. With the advent of Swift 3, I want to encourage you to use Swift 3's#keyPath()syntax to help you ensure the correctness of your property paths at compile time. Since#keyPath()returns a string value, it just made sense to switch over to using Strings now. However, this now gives you a chance to use PrediKit unsafely. Remember, with great power comes great responsibility. So I'll say it again:
DON'T STRINGIFY YOUR PROPERTIES, USE #KEYPATH FOR HAPPINESS INSTEAD!
- ⚠ First off, the use of PrediKit in Swift 3 caused a bunch of unused result warnings. This has been fixed by assigning the
-
v3.0.2 Changes
July 11, 2016Should solve #6
-
v3.0.1 Changes
May 31, 2016🚀 When including this as a subproject in another project, external CI builds fail due to minimum deployment targets being too high
-
v3.0 Changes
May 30, 2016💥 Breaking changes have been made as well. Most classes have been renamed for clarity and PrediKit.swift has been split up into manageable chunks in their own files for any potential contributors.
👍 We've also added support for passing in instances of NSArray to the matchesAnyValueIn query.
-
v2.0.6 Changes
May 30, 2016Oops! I did it again.
-
v2.0.5 Changes
May 30, 2016📜 Arguments weren't being parsed or handled correctly for arbitrary includer combination arrangements. This caused arguments to be switched around. We now respect the order of the combinations specified by the developer as the Great Gatsby intended it.
-
v2.0.4 Changes
May 29, 2016👍 Aco Taco. I touted OSX support but didn't actually do it. Whoopsies that should be remedied now!