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
Apologies if this is covered in the documentation already - but I'm trying to find the right entry point to implement a general input validation (for example to reject any input variables that contain potentially unsafe characters in the associated values). I couldn't reason creating a Plugin or using a custom Rule for the StaticValidation flows for this purpose and am wondering if there is any recommendation for such a use case.
The text was updated successfully, but these errors were encountered:
alisaifee
changed the title
[Question]: Implementing input variable validation across the entire schema
[Question]: Implementing input validation across the entire schema
Apr 28, 2024
That way, those arguments will use AsciiString's input validation. As a bonus, the schema's generated documentation will inform clients of the special requirements of that string, since it's an AsciiString, not a plain String. (If your validation isn't .ascii_only?, then use your validation code there instead.)
Thank you for the prompt reply @rmosolgo. This is definitely an approach I can work with and having the explicit scalar lending to better documentation of the expectation is a big bonus!
Description
Apologies if this is covered in the documentation already - but I'm trying to find the right entry point to implement a general input validation (for example to reject any input variables that contain potentially unsafe characters in the associated values). I couldn't reason creating a
Plugin
or using a customRule
for theStaticValidation
flows for this purpose and am wondering if there is any recommendation for such a use case.The text was updated successfully, but these errors were encountered: