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
{{ message }}
Repository navigation
Matching errors without checking NSError's userInfo dictionary #615
But it may be good to provide another overload which takes an NSError and a matching strategy such as:
enumNSErrorMatchingStrategy{case`default` // Rely on `NSError`'s `Equatable` implementation
caseignoringUserInfo // Just compare `domain` and `code` and ignore `userInfo`
}funcmatchError(_error:NSError,strategy:NSErrorMatchingStrategy=.default)->Predicate<NSError>
Activity
ikesyo commentedon Jan 20, 2019
I'm sorry for the late response.
I think that's because
NSErrorequality check is implemented as such and the overload is used:Nimble/Sources/Nimble/Matchers/MatchError.swift
Lines 34 to 53 in 025d0e2
So I'd say this is an expected behavior.
But it may be good to provide another overload which takes an
NSErrorand a matching strategy such as: