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
{{ message }}
This repository has been archived by the owner on May 12, 2018. It is now read-only.
I want to continue the discussion from #130: I have full understanding that you want to limit the scope of the library to what is supported by the specification.
My problem is, that there is right now no possibility to intercept the validation process.
I really need this feature and hence I kindly ask for your support. Aside from the requested change I see two other ways to make the validation interceptable. Maybe one of those is causing less maintenance, etc. effort.
Hi Matt,
I want to continue the discussion from #130: I have full understanding that you want to limit the scope of the library to what is supported by the specification.
My problem is, that there is right now no possibility to intercept the validation process.
json-guard/src/Validator.php
Lines 270 to 272 in 85c5611
I really need this feature and hence I kindly ask for your support. Aside from the requested change I see two other ways to make the validation interceptable. Maybe one of those is causing less maintenance, etc. effort.
1. Move the validation logic to the ruleset
Validator.php
RuleSetContainer.php
2. Make Validator.php extendable
i.e. remove the final keyword and make validateRule protected instead of private.
Looking forward to your feedback!
The text was updated successfully, but these errors were encountered: