feat: added docs and test for P.object.exact(..)

[JUSTIVE]

adds docs, and tests for P.object.exact

Todos:

• write docs for P.object.exact
• write test for P.object.exact

[JUSTIVE]

currently, {} could be caught by P.object.exact({a: P.any}) pattern.

[JUSTIVE]

fixed {} caught by {a:P.any}, but nested object pattern should be tested

[gvergnaud]

Thanks for contributing! A few comments

[gvergnaud]

Is it to force people to include any key that exist's on an object? I think that makes a lot of sense, but how does it behave when the input has type unknown and any? Could you add tests for that?

[JUSTIVE]

during the implementation of this feature, I'm concerned about the following scenarios.

1. nested object, but an exact match for the outer side, and less strict matching inside. (the other way, less strict matching outside and strict inside makes sense, but not this one.)
2. recursive objects.

maybe we need to consider those cases first before implementing it.

[gvergnaud]

I was think that exact({ ... }) would only apply to the current level of nesting. If you want everything to be exact, then you need to nest exacts as well:

P.object.exact({
   // this object should only have a single `a` key
   a: {
      // this object must have at least a `b` key that's a string.
      b: P.string
   }
})

If you want everything to be exact you'd do:

 P.object.exact({
   a: P.object.exact({
      b: P.string
   })
})

Do you find a problem with that? What are the scenarios that worry you?

[JUSTIVE]

I think that behavior could easily cause misunderstanding. I thought exact should catch 'exact' object matching, not 'exact matching, but only single depth'. It's a bit ambiguous.

[JUSTIVE]

I'll keep implementing with single-depth match version(because it's a sub-spec of full-depth matching), but still not sure it's good design or not.