'toBeHexadecimal' is a disguise name

[sergiuchuckmisha]

First of all: I understand that, according to documentation, behavior is correct. What I mean is that name of method toBeHexadecimal is disguise. toBeHTMLHexadecimalColor or toBeHexadecimalColor would be better naming.

Bug

• package version: "jest-extended": "^0.11.1"
• node version: v10.13.0
• npm version: 6.4.1

Relevant code or config

expect("cb2f450864cceab1632939e35554d20cc8d9f38e688fa1e68a4b408f90b1f978").toBeHexadecimal();

What you did: tried to verify is string a valid hash

What happened (please provide anything you think will help): test failed Reproduction repository (if possible): not possible

Possible solution:

• rename toBeHexadecimal to toBeHTMLHexadecimalColor or to toBeHexadecimalColor

• possibly, add method toBeHexadecimal which checks if a value is a valid hexadecimal string.

[hiwelo]

👍

Is there any update regarding this issue? I would definitely push for the removal of the size requirement for the toBeHexadecimal matcher, especially because the current matcher is not even working with the "new" format of hexadecimal colors that can have up to 8 chars (when having alpha information for the color).

In this case, we could have:

• toBeHexadecimal() as a matcher for any hexadecimal string
• toBeHexColor() as a matcher for hexadecimal color strings having 3 to 8 chars

Another solution would be to have only toBeHexadecimal as a matcher for all hexadecimal string with an optional parameter with a maximum amount of chars for the provided string.