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
As it currently exists, a previous comment of mine discusses the addition of some simple validators. I created this issue as a potential easy pickup for beginners to assist in the go etherium project.
As it stands, go-validator and similar packages provide an easier way to handle validation steps in an easy to understand, expandable, and customizable way for any struct with custom fields and functions for validation. Including some built in validators.
This issue, is an open epic for adding some number of validators elsewhere in etherium using this idiomatic golang library support to provide this value add for the go-etherium project.
above is the validation function, using go-validate, which would then run the validation and return an error inline.
This is a much more go-thonic and sustainable way to do validation throughout etherium. This could compromise a substantial value add for other areas of the etherium project as well, providing more sustainable and expandable validation in many areas of the codebase.
This is too much of a meta issue. If you wish to debate specific instances, you're more than welcome - and support them with code examples - but just opening an issue to "add validations everywhere" is not useful.
As it currently exists, a previous comment of mine discusses the addition of some simple validators. I created this issue as a potential easy pickup for beginners to assist in the go etherium project.
As it stands, go-validator and similar packages provide an easier way to handle validation steps in an easy to understand, expandable, and customizable way for any struct with custom fields and functions for validation. Including some built in validators.
This issue, is an open epic for adding some number of validators elsewhere in etherium using this idiomatic golang library support to provide this value add for the go-etherium project.
above is the validation function, using go-validate, which would then run the validation and return an error inline.
This is a much more go-thonic and sustainable way to do validation throughout etherium. This could compromise a substantial value add for other areas of the etherium project as well, providing more sustainable and expandable validation in many areas of the codebase.
Originally posted by @wsb1994 in #27876 (comment)
The text was updated successfully, but these errors were encountered: