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

issues #169 #598

Closed
ligf opened this Issue Jun 26, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@ligf

ligf commented Jun 26, 2017

@logaretm

This comment has been minimized.

Show comment
Hide comment
@logaretm

logaretm Jun 29, 2017

Collaborator

Can you better describe the issue? I can only see that the two fields (pass and pass confirm) are working and displaying errors properly.

Also Few stuff has been fixed since RC3, is there a specific reason that prevents you from upgrading to rc.5 or rc.6?

Collaborator

logaretm commented Jun 29, 2017

Can you better describe the issue? I can only see that the two fields (pass and pass confirm) are working and displaying errors properly.

Also Few stuff has been fixed since RC3, is there a specific reason that prevents you from upgrading to rc.5 or rc.6?

@ligf

This comment has been minimized.

Show comment
Hide comment
@ligf

ligf Jul 2, 2017

1
I use cdn "https://cdn.jsdelivr.net/npm/vee-validate@latest/dist/vee-validate.js".
The rules is "data-vv-rules="required|confirmed:AdminPassConfirm"" in the code .
I want the error to show that the content is "确认密码" but it shows "AdminPassConfirm".

ligf commented Jul 2, 2017

1
I use cdn "https://cdn.jsdelivr.net/npm/vee-validate@latest/dist/vee-validate.js".
The rules is "data-vv-rules="required|confirmed:AdminPassConfirm"" in the code .
I want the error to show that the content is "确认密码" but it shows "AdminPassConfirm".

@logaretm logaretm added bug and removed more information needed labels Jul 2, 2017

@logaretm logaretm closed this in 5b6f0dc Jul 6, 2017

@logaretm

This comment has been minimized.

Show comment
Hide comment
@logaretm

logaretm Jul 6, 2017

Collaborator

I have identified the issue and solved it using the latest changes in master, Should be released with the next release.

Collaborator

logaretm commented Jul 6, 2017

I have identified the issue and solved it using the latest changes in master, Should be released with the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment