You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The isHexColor function in validator.js currently allows strings like "6633FF" to pass validation as a valid hex color, even though a proper hex color should include a leading #. This issue arises from the current regex implementation in the library.
A PR has just been opened for this; #2535
I would say this is intended behaviour in isHexColor. Although HTML and CSS do require a leading #, I think this has been in the project for so long and with the current amount of downloads it could become a breaking change impacting a lot of applications.
What we could do is allow a new option, requireHashtag or something similar, that enforces this behaviour.
The isHexColor function in validator.js currently allows strings like "6633FF" to pass validation as a valid hex color, even though a proper hex color should include a leading #. This issue arises from the current regex implementation in the library.
https://github.com/validatorjs/validator.js/blob/master/src/lib/isHexColor.js
Is allowing hex colors without # an intended behavior in isHexColor? If not, can I submit a fix?
The text was updated successfully, but these errors were encountered: