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 Jan 22, 2020. It is now read-only.
Typically for web development is you validate and sanitize parameters on client and server side. Legalize makes it possible to use the same schema for both. Sanitizing strings regarding html entities, country codes, lanugage codes or character encodings is also possible but you have to search the internet for appropriate lists first.
An additional module which comes with (just) static lists/arrays that you need for typical parameter sanitizing would enhance the usability of legalize, especially when someone builds a globalized web page. Those lists could then be used with the sanitize methods of legalize.
That would make validation and sanitization possible out of "one hand" instead of being forced to use several different modules => reduces app complexity and search and learning curve of developers.
The text was updated successfully, but these errors were encountered:
Sounds interesting. I believe this implies having a plugin-system in place which would allow the addition of validators much in the same way like jquery plugins.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Typically for web development is you validate and sanitize parameters on client and server side. Legalize makes it possible to use the same schema for both. Sanitizing strings regarding html entities, country codes, lanugage codes or character encodings is also possible but you have to search the internet for appropriate lists first.
An additional module which comes with (just) static lists/arrays that you need for typical parameter sanitizing would enhance the usability of legalize, especially when someone builds a globalized web page. Those lists could then be used with the sanitize methods of legalize.
That would make validation and sanitization possible out of "one hand" instead of being forced to use several different modules => reduces app complexity and search and learning curve of developers.
The text was updated successfully, but these errors were encountered: