GoValidator

GoValidator is a robust and versatile Go package that streamlines the process of validating data through struct information. Designed to simplify and enhance input data validation for your Go applications, GoValidator empowers developers to effortlessly validate data

Key Features:

• Simple and Intuitive Validation: Easily validate user input by adding validation tags to your struct fields.

• Support for Common Validation Rules: The package supports a variety of common validation rules, including:

  • Required fields
  • Maximum and minimum lengths for strings
  • Email format validation
  • URL format validation
  • Active URL validation
  • IP address format validation
  • Date format validation
  • Between validation
  • In validation

Installation

To install this package, you can use the go get command:

go get github.com/sCuz12/goinputvalidator

Usage

type User struct {
	Title        string `validate:"required|max:10|min:2"`
	Body         string `validate:"required"`
	Email        string `validate:"email|required"`
	Website      string `validate:"url"`
	ActiveURL    string `validate:"active_url"`
	IPAddress    string `validate:"ipformat"`
	Birthdate	 string `validate:"date"`
	AllowAge	 int    `validate:"between:1,40"`
	UserType 	 string `validate:"in:driver,client,admin"`,
	Subscription string`validate:"notIn:free,freebie"`
	SendEmails 	 interface{} `validate:"accepted"`
   Fields		[]string `validate:"size:2"`
   Confirmation_password string 
	Password 	string `validate:"confirmed"`
   Smail		string  `validate:"doesnt_end_with:gmail.com"`
	Surname		string  `validate:"doesnt_start_with:geo"`
 	MacIP 		string  `validate:"macAddress"`
   DriveLicense int 	`validate:"gt:22"`
	WorkAge		int 	`validate:"lt:65"`
	YearsOld	int 	`validate:"gte:18"`
	MinYearsOld	int 	`validate:"lte:18"`
}

func main() {
	v := validator.New()

	user := User{
		Title:  	"This is a test",
		Body:       "Some body content",
		Email:      "[email protected]",
		Website:    "https://www.goooogle.com",
		ActiveURL:  "https://georgehadjisavva.dev",
		IPAddress:  "127.0.0.1",
		Birthdate:  "07-10-1995",
		AllowAge:	12,
		UserType: 	"client",
		Subscription : "free",
		SendEmails: 1,
      Fields: []string{"field1", "field2"},
      Confirmation_password : "password",
	   Password: 	"password1", 
      Smail: "[email protected]",
		Surname: "george",
      MacIP : "00:A0:CC:23:39:3F",
      DriveLicense: 25,
		WorkAge: 60,
		YearsOld: 18,
		MinYearsOld : 18,
	}

	err := v.Validate(user)

	if err != nil {
		for _,singleErr := range err {
			fmt.Println(singleErr)
		}
	}
}

---

Validation Documentation

1. Required

   • Rule Format: required
   • Example: validate:"required|max:20|min:2"
   • Description: Validates that the field is required and has a maximum length of 20 characters, with a minimum length of 2 characters.

2. Email

   • Rule Format: email
   • Example: validate:"email"
   • Description: Validates that the email is in a valid format

3. Website

   • Rule Format: url
   • Example: validate:"url"
   • Description: Validates that the website is a valid URL.

4. Active Website

   • Rule Format: active_url
   • Example: validate:"active_url"
   • Description: Validates that the website URL is active(accessible).

5. Ip Format

   • Rule Format: ipformat
   • Example: validate:"ipformat"
   • Description: Validates that the IP address is in a valid format.

6. Date

   • Rule Format: date
   • Example: validate:"date"
   • Description: Validates that the birthdate is in the allowed date formats
   • Notes: Acceptable formats
     • "YYYY/MM/DD" format, mapped to "2006/01/02".
     • "YYYY/DD/MM" format, mapped to "2006/02/01".
     • "YYYY-MM-DD" format, mapped to "2006-01-02".
     • "YYYY-DD-MM" format, mapped to "2006-02-01".

7. Date Format - Specify Format

   • Rule Format: dateFormat:YYYY-MM-DD
   • Example: validate:"dateFormat:YYYY-MM-DD"
   • Description: Validates that the birthdate is in the format specified "YYYY-MM-DD".

8. Between

   • Rule Format: between:floor,ceiling
   • Example: validate:"between:1,40"
   • Description: Validates that the input value is between the specified floor and ceiling values (inclusive).

9. In

   • Rule Format: in:value1,value2,...,valueN
   • Example: validate:"in:driver,client,admin"
   • Description: Validates that the input value is one of the specified allowed values.

10. Accepted

• Rule Format: accepted
• Example: validate:"accepted"
• Description: Validates if the input value is one of the accepted values: "yes", "on", 1, or true.

11. NotIn

• Rule Format: notin
• Example: validate:"notIn:free,freebie"
• Description: The NotIn validator ensures that the input value is not one of the specified disallowed values.

12. Size

• Rule Format: size:N

• Example: validate:"size:8"

• Description: Validates that the input data has a specific size. The behavior of this rule varies depending on the data type:

                 - For strings, "N" corresponds to the number of characters in the string.
                 - For arrays or slices, "N" corresponds to the number of elements in the array or slice.
  

13. Confirmed

• Rule Format: confirmed
• Example: validate:confirmed
• Description: Validates that a field matches its Confirmation_password counterpart. For example, it ensures that a Password field matches the Confirmation_password field to confirm that the user entered the correct password. This rule is used for password confirmation fields in registration or password reset forms.

14. Doesnt End With

• Rule Format: doesnt_end_with
• Example: validate:doesnt_end_with:gmail.com
• Description: Validates that a field does not end with a specified string. This rule is commonly used to ensure that a field, such as an email address, does not end with a specific domain or suffix. For example, it can be used to prevent registration with certain email domains. This rule provides an additional layer of validation for fields that should not have specific endings, such as email addresses, to enhance data integrity and security.

15. Doesnt Start With

• Rule Format: doesnt_start_with
• Example: validate:doesnt_start_with:geo
• Description: alidates that a field does not start with a specified string. This rule is commonly used to ensure that a field does not begin with specific prefixes or patterns. For instance, it can be applied to prevent usernames or passwords from starting with certain characters or sequences

16. Mac Address format

• Rule Format: macAddress
• Example: validate:"macAddress"
• Description: Validates that a field conforms to the standard format of a MAC address. A MAC address is a unique identifier assigned to network interfaces, often represented as six pairs of hexadecimal digits separated by colons or hyphens (e.g., "00:1A:2B:3C:4D:5E").

17. Greater Than

• Rule Format: gt:22
• Example: validate:"gt:22"
• Description: Validates that a field has a value greater than the specified threshold. For example, it can be used to ensure that an age field is greater than 22.

18. Greater Than Equal

• Rule Format: gte:18
• Example: validate:"gte:18"
• Description: Validates that a field has a value greater than or equal to the specified threshold. For example, it can be used to ensure that a score field is greater than or equal to 18.

19. Less Than

• Rule Format: lt:65
• Example: validate:"lt:65"
• Description: Validates that a field has a value less than the specified threshold. For example, it can be used to ensure that a temperature field is less than 65.

20. Less Than Equal

• Rule Format: lte:65
• Example: validate:"lte:65"
• Description: Validates that a field has a value less than or equal to the specified threshold. For example, it can be used to ensure that a price field is less than or equal to 65.