26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
#### Support
|
|
If you do have a contribution to the package, feel free to create a Pull Request or an Issue.
|
|
|
|
#### What to contribute
|
|
If you don't know what to do, there are some features and functions that need to be done
|
|
|
|
- [ ] Refactor code
|
|
- [ ] Edit docs and [README](https://github.com/asaskevich/govalidator/README.md): spellcheck, grammar and typo check
|
|
- [ ] Create actual list of contributors and projects that currently using this package
|
|
- [ ] Resolve [issues and bugs](https://github.com/asaskevich/govalidator/issues)
|
|
- [ ] Update actual [list of functions](https://github.com/asaskevich/govalidator#list-of-functions)
|
|
- [ ] Update [list of validators](https://github.com/asaskevich/govalidator#validatestruct-2) that available for `ValidateStruct` and add new
|
|
- [ ] Implement new validators: `IsFQDN`, `IsIMEI`, `IsPostalCode`, `IsISIN`, `IsISRC` etc
|
|
- [ ] Implement [validation by maps](https://github.com/asaskevich/govalidator/issues/224)
|
|
- [ ] Implement fuzzing testing
|
|
- [ ] Implement some struct/map/array utilities
|
|
- [ ] Implement map/array validation
|
|
- [ ] Implement benchmarking
|
|
- [ ] Implement batch of examples
|
|
- [ ] Look at forks for new features and fixes
|
|
|
|
#### Advice
|
|
Feel free to create what you want, but keep in mind when you implement new features:
|
|
- Code must be clear and readable, names of variables/constants clearly describes what they are doing
|
|
- Public functions must be documented and described in source file and added to README.md to the list of available functions
|
|
- There are must be unit-tests for any new functions and improvements |