feat: [#416] Support add custom filter for validation

[kkumar-gcc]

📑 Description

Closes goravel/goravel#416

✅ Checks

• Added test cases for my code

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.98%. Comparing base (0ad5442) to head (ce15251).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #516      +/-   ##
==========================================
+ Coverage   69.90%   69.98%   +0.07%     
==========================================
  Files         180      180              
  Lines       11000    11025      +25     
==========================================
+ Hits         7690     7716      +26     
+ Misses       2739     2738       -1     
  Partials      571      571              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hwbrzzl]

We need to define a filter interface and pass it here. Like the rule:

Add a command to create a filter.

[kkumar-gcc]

Nah, it's not a good idea since the filter function can vary.

[hwbrzzl]

Maybe:

type Filter interface {
	// Signature set the unique signature of the filter.
	Signature() string
	// Passes determine if the validation rule passes.
	Handle() func(val any) (any, error)
}

[hwbrzzl]

Nah, it's not a good idea since the filter function can vary.

We can only support one style: func(val any) (any, error)

[kkumar-gcc]

A developer can also create a filter function like this:

func Default(val string, def ...string) string {
    ...
}

which can be used like this:

map[string]string{
   "name" : "default:krishan"
}
// assume registered as "default"

So, let's not add constraints on developers since gookit/validate provides this feature.

[kkumar-gcc]

Maybe:

type Filter interface {
	// Signature set the unique signature of the filter.
	Signature() string
	// Passes determine if the validation rule passes.
	Handle() func(val any) (any, error)
}

we can change it to ?

type Filter interface {
	// Signature set the unique signature of the filter.
	Signature() string
	// Passes determine if the validation rule passes.
	Handle() any // will mention in docs that any can only be two type of function
}

[hwbrzzl]

We also need to add a new Filter method in the FormRequest:

Users can use the Filter feature through the Filter method, instead of set a tag in the struct:

The way of set a tag in the struct is inconsistent with the rule, so I suggest optimize it. cc @devhaozi

So we need to fdmovd the logic in goravel/gin and goravel/fiber and add some new logic:

[devhaozi]

LGTM

[hwbrzzl]

Great PR 👍 Please add some integration tests in goravel/example

[hwbrzzl]

Great