feat(expectations): add toMatch

[owenvoke]

Q	A
Bug fix?	no
New feature?	yes
Fixed tickets	#...

I wasn't sure about the naming of this, whether it should be toMatchRegEx, toMatchRegExp, or toMatchRegularExpression. (The toBe* prefix doesn't really work with any of them).

[olivernybroe]

What if we just call it toMatch instead?

Then let me do the following

expect('Hello World')->toMatch('/^hello wo.*$/i');
expect('Hello World')->toMatch('Hello World'); 

So a regex and a string is supported for matching.

[owenvoke]

@olivernybroe, that makes sense too. 👍🏻 Although, I wonder if people might get confused between toBe and toMatch. 🤔 @nunomaduro, what're your thoughts on this?

[olivernybroe]

@owenvoke Hmm true. Could we extend toBe to just support regex maybe?

[nunomaduro]

So, to give context. Normally, we mimic the API of Jest. In this case, Jest don't have this feature. So let's take a moment to actually make sure we don't make a mistake here.

JavaScript uses match : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/match.

I think we can use toMatchRegex for now, and change it later if we think people will be confortable with an toMatch.

[olivernybroe]

@nunomaduro According to jest they use toMatch in their expect api
Which can take a string and a regex or am I misunderstanding something here? 👍

https://jestjs.io/docs/en/expect#tomatchregexporstring

[nunomaduro]

@owenvoke @olivernybroe If Jest uses toMatch, let's use toMatch too. 👍

[owenvoke]

Pushed an update. 👍🏻

[nunomaduro]

Fell free to merge, tag a new version, update the docs, and make a tweet about it @owenvoke .

[owenvoke]

@nunomaduro, I noticed you merged the docs for toMatchConstraint. Do you want me to merge #190 as well and include that in v0.3.6?

[nunomaduro]

@owenvoke Yes.