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
The values passed to a/an matchers seem to correspond to the type-detect library's results reported for specific objects. That means that since that library got introduced, e.g. new Error(...) is no longer detected as a object and is now detected as an error instead.
Could the documentation on those matchers be updated?
The text was updated successfully, but these errors were encountered:
I'll point out that the site has yet to be updated - it's getting quite stale but we need to spend some time redeveloping it to have automated builds.
The documentation for an is here (L127-155 of assertions.js) and the docs have been updated for the new behaviour (with an exception of Error missing). Feel free to include error as an example, and when the new site gets built it'll be reflected!
The values passed to
a
/an
matchers seem to correspond to thetype-detect
library's results reported for specific objects. That means that since that library got introduced, e.g.new Error(...)
is no longer detected as aobject
and is now detected as anerror
instead.Could the documentation on those matchers be updated?
The text was updated successfully, but these errors were encountered: