Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Validator BUG #2515

Closed
lingcoder opened this issue Mar 10, 2023 · 1 comment
Closed

Custom Validator BUG #2515

lingcoder opened this issue Mar 10, 2023 · 1 comment
Labels
bug It is confirmed a bug, but don't worry, we'll handle it. done This issue is done, which may be release in next version.

Comments

@lingcoder
Copy link
Contributor

1. What version of Go and system type/arch are you using?

go version go1.20.1 windows/amd64

2. What version of GoFrame are you using?

GoFrame CLI Tool v2.3.3

3. Can this issue be re-produced with the latest release?

YES

4. What did you do?

When I use the custom validation tag and registered it, I found that the default message cannot be displayed correctly. The placeholders for field and value are not replaced correctly.

5. What did you expect to see?

{"code": 51,
"msg": "The Address value 0xabcdefg is invalid",
"data": null
}
{

6. What did you see instead?

{"code": 51,
"msg": "The {field} value {value} is invalid",
"data": null
}
{

@Issues-translate-bot Issues-translate-bot changed the title Custom Validator BUG Custom Validator BUG Mar 10, 2023
@zcyc
Copy link
Contributor

zcyc commented Mar 13, 2023

same to #2499
fix in #2505

@gqcn gqcn added the bug It is confirmed a bug, but don't worry, we'll handle it. label Mar 13, 2023
gqcn added a commit that referenced this issue Mar 13, 2023
gqcn added a commit that referenced this issue Mar 13, 2023
@gqcn gqcn added the done This issue is done, which may be release in next version. label Mar 14, 2023
@gqcn gqcn closed this as completed Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It is confirmed a bug, but don't worry, we'll handle it. done This issue is done, which may be release in next version.
Projects
None yet
Development

No branches or pull requests

3 participants