Use Custom DSL instead of Inheriting NUnit.Framework.Is

[lilasquared]

Is your feature request related to a problem? Please describe.
Suppose I had multiple NUnit extensions similar to Snapper, I would not be able to use all Is DSL methods in a single file without using FQDN of the Is Class

ex:
Assert.That(obj, Snapper.Nunit.Is.EqualToSnapshot());

Describe the solution you'd like
I think it would be more declarative and composable to have a custom class, something specific to the domain of Snapper.

ex:
Assert.That(obj, Matches.Snapshot());
Assert.That(obj, Matches.ChildSnapshot("some-snap"));

Great work with this library, I was actually the one who opened nunit/nunit#2392 in the Nunit repo, and this is exactly what I was envisioning!

[theramis]

Hey @lilasquared,

Sorry for the late reply, had a bit of a break and only focused on bugs for a bit.
I like the solution you are suggesting and I reckon I'll probably implement it.

I'm not sure how/when to release this though. It would be a breaking change if I got rid of Snapper.Nunit.Is.

Maybe I'll add the new Matches class and mark the Snapper.Nunit.Is class as deprecated with a minor bump of the package.

Then in a future major bump I'll remove the Snapper.Nunit.Is class.

Thoughts?

[lilasquared]

I think that makes the most sense. Thanks!

[theramis]

@all-contributors please add @lilasquared for ideas

[allcontributors]

@theramis

I've put up a pull request to add @lilasquared! 🎉

[theramis]

Released in v2.3.0