Make s.object() confirm to the standard matcher(options)

[rprieto]

Strummer matchers usually have several forms:

• a canonical version which takes options, like like s.array({of: matcher, min :1})
• shorthand helpers like s.array(matcher)

object is the only exception, because the canonical version is s.object(fields). This means the matcher can never have an other options. It would be a breaking change, but I suggest we should change to s.object({props: ...}), which would allow for things like

s.object({
  optional: true,     // can be null
  allowExtra: true,   // don't fail if there's additional properties to the ones below
  props: { ... }      // list of properties
})

We could still have the top-level shorthand s(someObject) which would delegate to s.object({props: someObject}).

Note: this would remove the need for s.objectOnly.

[kiddkai]

sounds good to me~

[FagnerMartinsBrack]

Could also do something like:

s.object({with: properties})

Which would kind of be read in a similar way as "object with only properties", just now it would be "object with properties" (which IMHO is much more fluent).

It is very important that we run strict comparisons by default and only allow ignoring properties if explicitly asking to do so.

👍

[rprieto]

👍 for s.object({with: properties})