What I was trying to say is that we should first parse and then check if the phone number matches.

Otherwise, we can have an especial situation where a name includes a pattern that could be identified as a phone unproperly.

For example:

<Foo +1-123-123-1234> +1-999-999-9999 156 Alphand_St.

If we search for the phone number +1-123-123-1234, this solution will identify that record, but should not, since the phone number is +1-999-999-9999.

It might sound over, but exceptions happens and we should provide solutions that works safely.

name between < and >

Approved

Lua translation !

merged

js fork

• make description language-agnostic
• enable node 18
• use mocha/chai assertions
• use lodash for randomness
• provide input on failure
• get rid of refsol
• ensure balanced number of test for both cases

great, I agree, your code should be short and fast at the same time.

why?

Should be fixed by the fork above.

Approved by someone

PHP fork:

• fixing broken ref. solution.
• add input string to fail message

should fix this issue.

In PHP random tests, "irtaq" or "qohnito" or "tonqikuko" expects to be true. Is that correct? Or a bug in author's solution.

done