All Versions
22
Latest Version
Avg Release Cycle
47 days
Latest Release
2295 days ago

Changelog History
Page 2

  • v2.0.1 Changes

    👀 1. [YDB-41]: Removes FRP extensions which don’t support Swift 2.0 yet.

  • v2.0.0 Changes

    👀 1. [YDB-38]: Preparations for Swift 2.0.

  • v1.8.0 Changes

    👀 1. [YDB-36]: Sets the required version of BrightFutures to the latest for Swift 1.2, which is 2.0.1. 👀 2. [YDB-37]: Sets the required version of PromiseKit to the latest for Swift 1.2, which is 2.2.1 (as submitted to CocoaPods).

  • v1.7.0 Changes

    👀 1. [YDB-25]: Adds YapDB.Search to aid with running FTS queries. An example of using with will be forthcoming (probably after Swift 2.0 has settled). But essentially, you can initialize it with your db, an array of YapDB.Fetch values (which should be views) and a string mapper. Then execute usingTerm(term: String) with the search term supplied by the user to run the search. 👀 2. [YDB-26]: Adds some missing default parameters for the YapDB.SecondaryIndex wrapper. 👀 3. [YDB-27]: Removes an explicit unwrap which could cause a crash if pattern matching against value types. 👀 4. [YDB-29]: Adds support to YapDatabaseConnection for writeBlockOperation (NSBlockOperation), write and remove APIs. This is great if you want to perform a number of writes of different types in the same transaction inside of an NSOperation based architecture, as you can do:

    queue.addOperation(connection.writeBlockOperation { transaction in 
    transaction.write(foo)
    transaction.write(bar)
    transaction.remove(bat)
})

    If you're using my Operations framework, as these operations are NSBlockOperations, use ComposedOperation to attach conditions or observers. E.g.

    let write = ComposedOperation(connection.writeBlockOperation { transaction in 
    transaction.write(foo)
    transaction.write(bar)
    transaction.remove(bat)
})
write.addCondition(UserConfirmationCondition()) // etc etc
queue.addOperation(write)

    👀 5. [YDB-30]: Expands the YapDB.Mappings type to support the full YapDatabaseViewMappings gamut. 👀 6. [YDB-31]: Silences a warning in the removeAtIndexes API.

  • v1.6.0 Changes

    👀 1. [YDB-22]: Adds YapDB.Fetch.Index which wraps YapDatabaseSecondaryIndex extension. 🚀 2. [YDB-23]: Fixes a crash which has been observed in some cases in a Release configuration where writing a value type can fail to get the type’s Archiver. 👀 3. [YDB-24]: Just cleans up some of the code.

  • v1.5.0 Changes

    👀 1. [YDB-19]: Implements Saveable on YapDB.Index. This makes it easier to store references between YapDatabase objects. In general this is preferable to storing references as let fooId: Foo.IdentifierType. 👀 2. [YDB-21]: Restructures the project. The framework is now in an Xcode project in framework, with its associated unit tests in place. This is in preparation for Xcode 7, to get code coverage of the framework. The Example has been moved to examples/iOS, although it doesn’t really do much, except provide some models.

  • v1.4.0 Changes

    👀 1. [YDB-16]: Adds helper APIs for creating a YapDatabase. Includes a function for creating temporary database for use inside unit tests.

  • v1.3.0 Changes

    📇 1. [YDB-1]: Adds API for reading metadata, additionally fixes bugs where writing types with metadata would fail when using database or connections. 📚 1. [YDB-15]: Updates README documentation.

  • v1.2.0 Changes

    📚 1. [YDB-6]: Improves the code documentation significantly. Updates the README. 👀 1. [YDB-12]: Improves and adds to the test coverage. Fixes an oversight where keys and indexes were not uniqued before accessing the database.

  • v1.1.1 Changes

    👀 1. [YDB-11]: Renames YapDatabase.Index to YapDB.Index.