Fetchable members comparisons support

Comparison between n attribute and the attribute of a relationship.

Example

User.request()
    .all()
    .where { $0.score == $0.friend.score }

FetchableValue

Removed DatabaseValue and DatabaseTestValue protocol in favor of a single protocol FetchableValue to make it easier for complex types to be used in a predicate.

Also added support for NSManagedObject and NSManagedObjectID comparison and to-many relationship contains operator.

Issues

#28
#29

Initial Stable Release

1.0.0

Updated doc

Replaced key paths by fetchable members

Changed

• Moved away from KeyPaths to user FetchableMembers specified for each entity, using a macro or manually.
• Predicate writing has changed to use fetchable members, which feels more natural in Swift, and restrict fetching ton only available members
• FetchableManagedObject macro to conform to Fetchable and add fetchable members.
• Entity comparison is now supported again

Warning

This is a breaking change.

This version will most likely evolve into a stable 1.0.0 release.

Replaced key paths by fetchable members

Changed

• Moved away from KeyPaths to user FetchableMembers specified for each entity, using a macro or manually.
• Predicate writing has changed to use fetchable members, which feels more natural in Swift, and restrict fetching ton only available members
• FetchableManagedObject macro to conform to Fetchable and add fetchable members.
• Entity comparison is now supported again

Warning

This is a breaking change.

This version will most likely evolve into a stable 1.0.0 release.

Replaced key paths by fetchable members

Changed

• Moved away from KeyPaths to user FetchableMembers specified for each entity, using a macro or manually.
• Predicate writing has changed to use fetchable members, which feels more natural in Swift, and restrict fetching ton only available members
• FetchableManagedObject macro to conform to Fetchable and add fetchable members.
• Entity comparison is now supported again

Warning

This is a breaking change.

This version will most likely evolve into a stable 1.0.0 release.

Replaced key paths by fetchable members

Changed

• Moved away from KeyPaths to user FetchableMembers specified for each entity, using a macro or manually.
• Predicate writing has changed to use fetchable members, which feels more natural in Swift, and restrict fetching ton only available members
• FetchableManagedObject macro to conform to Fetchable and add fetchable members.

Warning

This is a breaking change.

This version will most likely evolve into a stable 1.0.0 release.

Handle optionals in KeyPaths

0.8.1

Handle optionals in Key paths

Removed StringKeyPaths

Since KeyPaths have now a description, it's unneeded to use NSExpression, and it's possible to directly use key path to computed properties.

Fixed backslash escaping

Merge pull request #24 from ABridoux/develop

Fixed backslash escaping