session-ios/SignalMessaging/environment/migrations/OWS101ExistingUsersBlockOnI...

//
//  Copyright (c) 2018 Open Whisper Systems. All rights reserved.
//

#import "OWS101ExistingUsersBlockOnIdentityChange.h"
#import <YapDatabase/YapDatabaseTransaction.h>

NS_ASSUME_NONNULL_BEGIN

// Increment a similar constant for every future DBMigration
static NSString *const OWS101ExistingUsersBlockOnIdentityChangeMigrationId = @"101";

/**
 * This migration is no longer necessary, but deleting a class is complicated in Yap
 * and involves writing another migration to remove the previous. It seemed like the
 * simplest/safest thing to do would be to just leave it.
 */
@implementation OWS101ExistingUsersBlockOnIdentityChange

+ (NSString *)migrationId
{
    return OWS101ExistingUsersBlockOnIdentityChangeMigrationId;
}

- (void)runUpWithTransaction:(YapDatabaseReadWriteTransaction *)transaction
{
    OWSAssertDebug(transaction);

    OWSFailDebug(@"[OWS101ExistingUsersBlockOnIdentityChange] has been obviated.");
}

@end

NS_ASSUME_NONNULL_END
IdentityKeyStore changes 1) Always accept keys from incoming messages 2) Block sending only if it's a recent change, or if always block is enabled // FREEBIE // FREEBIE 9 years ago			`//`
Don't mark app as ready until all version migrations are done. 8 years ago			`// Copyright (c) 2018 Open Whisper Systems. All rights reserved.`
IdentityKeyStore changes 1) Always accept keys from incoming messages 2) Block sending only if it's a recent change, or if always block is enabled // FREEBIE // FREEBIE 9 years ago			`//`
Changed Safety numbers no longer block communication When your partner changes their identity key (e.g. by reinstalling), you'll see a notice alongside their message, but it will no longer prevent the message from showing. aka "non blocking". Existing users will be opted into the previous blocking behavior. This is configurable for all users in Settings > Privacy. // FREEBIE 9 years ago
			`#import "OWS101ExistingUsersBlockOnIdentityChange.h"`
			`#import <YapDatabase/YapDatabaseTransaction.h>`

			`NS_ASSUME_NONNULL_BEGIN`

			`// Increment a similar constant for every future DBMigration`
			`static NSString *const OWS101ExistingUsersBlockOnIdentityChangeMigrationId = @"101";`

style cleanup, no functional changes // FREEBIE 9 years ago			`/**`
			`* This migration is no longer necessary, but deleting a class is complicated in Yap`
			`* and involves writing another migration to remove the previous. It seemed like the`
			`* simplest/safest thing to do would be to just leave it.`
			`*/`
Changed Safety numbers no longer block communication When your partner changes their identity key (e.g. by reinstalling), you'll see a notice alongside their message, but it will no longer prevent the message from showing. aka "non blocking". Existing users will be opted into the previous blocking behavior. This is configurable for all users in Settings > Privacy. // FREEBIE 9 years ago			`@implementation OWS101ExistingUsersBlockOnIdentityChange`

			`+ (NSString *)migrationId`
			`{`
			`return OWS101ExistingUsersBlockOnIdentityChangeMigrationId;`
			`}`

			`- (void)runUpWithTransaction:(YapDatabaseReadWriteTransaction *)transaction`
			`{`
Step 2/2 %s/OWSAssert/OWSAssertDebug for existing previous assert semantics Going forward, we want to prefer safer asserts, but we don't want to blindly apply crashing asserts across the codebase 7 years ago			`OWSAssertDebug(transaction);`
Don't mark app as ready until all version migrations are done. 8 years ago
Rename fail macros in Obj-C. 7 years ago			`OWSFailDebug(@"[OWS101ExistingUsersBlockOnIdentityChange] has been obviated.");`
Changed Safety numbers no longer block communication When your partner changes their identity key (e.g. by reinstalling), you'll see a notice alongside their message, but it will no longer prevent the message from showing. aka "non blocking". Existing users will be opted into the previous blocking behavior. This is configurable for all users in Settings > Privacy. // FREEBIE 9 years ago			`}`

			`@end`

			`NS_ASSUME_NONNULL_END`