You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that in branch 3.0, a fix that was done in 2.x concerning name prefixes of entities in Swift has been removed from NSManagedObject, in -MR_entityName
OLD (v 2.0) - Working:
+ (NSString *) MR_entityName;
{
NSString *entityName;
if ([self respondsToSelector:@selector(entityName)])
{
entityName = [self performSelector:@selector(entityName)];
}
if ([entityName length] == 0)
{
// Remove module prefix from Swift subclasses
entityName = [NSStringFromClass(self) componentsSeparatedByString:@"."].lastObject;
}
return entityName;
}
The reason it doesn't work for me in Swift, is because it doesn' handle the entity names containing the Module name in the class. Is there any reason why this fix didn't make it from version 2 to version 3? Even if Xcode 7 has made changes to Core Data entity names, having your core data entities in a shared embedded framework (which is my case) still prefixes the names of the classes, so in my opinion, the fix should be preserved from version 2 to version 3.
Is it valid to transfer it, or there is a reason why this was omitted in 3.0?
The text was updated successfully, but these errors were encountered:
Hello,
I noticed that in branch 3.0, a fix that was done in 2.x concerning name prefixes of entities in Swift has been removed from NSManagedObject, in
-MR_entityName
OLD (v 2.0) - Working:
NEW (v 3.0) - Not working
The reason it doesn't work for me in Swift, is because it doesn' handle the entity names containing the Module name in the class. Is there any reason why this fix didn't make it from version 2 to version 3? Even if Xcode 7 has made changes to Core Data entity names, having your core data entities in a shared embedded framework (which is my case) still prefixes the names of the classes, so in my opinion, the fix should be preserved from version 2 to version 3.
Is it valid to transfer it, or there is a reason why this was omitted in 3.0?
The text was updated successfully, but these errors were encountered: