Florian

That's exactly what [`findOrCreate(for:in:)`](https://github.com/ffried/FFCoreData/blob/master/FFCoreData/FFCoreData/NSManagedObject/CoreDataDecodable.swift#L27) is for. While the default implementation fetches a "singleton-like" object and updates it, you can always implement it in your entities and fetch an object with...

I've just released [v4.1.0](https://github.com/ffried/FFCoreData/releases/tag/4.1.0) which adds the above convenience extension. However, this still does not deal with decoding say an array of entities. There you still need to manually loop...

@nhgrif Thanks for proposing and implementing this change! For the rest of the team here: I've already outlined on Stack Overflow that having custom log levels in Swift is currently...

@nhgrif I just realized it should probably be `NS_TYPED_EXTENSIBLE_ENUM` instead of `NS_OPTIONS`. 👀 `NS_OPTIONS` is an `OptionSet` in Swift. However, a log message can only be logged with one level...

Good point. Although that requires some code changes first. But yea, we should also mention that in the docs then.

Are you using a subclass of `DDLogFileManagerDefault`? If so, I could see both issues coming from an incomplete implementation: The default log file name uses the following pattern as log...

@oyljerry Can you try with the lastest state of `master`? There has been a change made in #1287 that _might_ resolve that problem.

@oyljerry @coolwuzizai I just went through all the changes since 3.7.0 and I really can't seem to figure out what's wrong. I've just pushed a small change (cf6e7e0b2ebfe7cc741530fda03950284e9d28df) that _might_...

Thanks for bringing this to our attention! IMHO this needs a team discussion here (pinging @CocoaLumberjack/collaborators). My two cents: I think CocoaLumberjack doesn't have too many references. The blacklist/whitelist ones...

The code part of this (#1218) just went live in 3.7.1 🙂