Open staabm opened 3 years ago
+1
This is an interesting idea for sure!
I'll put some thought into this, might be a good idea to split this package like you suggest.
I too would love this. I just spent time porting this to Symfony. Even if it's the same package, and doesn't have a hard dependency on laravel (use suggests instead?), that would be fine. The rules really aren't dependent upon Laravel other than using it's signature. It could be extracted to a separate namespace, one for the laravel rule integration which depends upon the agnostic implementation for checking a password against a rule.
I would love to use the nist-password-rules part of this package in applications which are not built on laravel.
do you think it would be possible to devide this package into 2 parts.. one only containg of the nist-password-rules part and another one which bridges this nist-password-rules with laravel?