-
Notifications
You must be signed in to change notification settings - Fork 555
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
635ecdb
commit 6c3cb32
Showing
5 changed files
with
205 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
#### 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 [https://github.com/asaskevich/govalidator/README.md](README): spellcheck, grammar and typo check | ||
- [ ] Create actual list of contributors and projects that currently using this package | ||
- [ ] Resolve [https://github.com/asaskevich/govalidator/issues](issues and bugs) | ||
- [ ] Update actual [https://github.com/asaskevich/govalidator#list-of-functions](list of functions) | ||
- [ ] Update [https://github.com/asaskevich/govalidator#validatestruct-2](list of validators) that available for `ValidateStruct` and add new | ||
- [ ] Implement new validators: `IsFQDN`, `IsIMEI`, `IsPostalCode`, `IsISIN`, `IsISRC` etc | ||
- [ ] Implement [https://github.com/asaskevich/govalidator/issues/224](validation by maps) | ||
- [ ] 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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters