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.

Sign up for GitHub

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

Jump to bottom

form values will be covered by the initialValue value of usefield #4846

Open
2 of 5 tasks
byronogis opened this issue Aug 26, 2024 · 1 comment · May be fixed by #4847
Open
2 of 5 tasks

form values will be covered by the initialValue value of usefield #4846

byronogis opened this issue Aug 26, 2024 · 1 comment · May be fixed by #4847

Comments

@byronogis
Copy link

byronogis commented Aug 26, 2024 •
edited
Loading

What happened?

// component A
// there is already have a form (by useForm), 
const {
  values,
  setValues,
} = useForm()

// and then use setValues to set a new value, 
setValues({
  name: 'x',
})

// component B
// create a new field (by useField, and have a avaliable initialValue y)
const {
  value
} = useField('name', undefined, {
  initialValue: 'y'
})

when the compoent B is dynamic create, the name will y not x

"vee-validate": "^4.13.2",
"vue": "^3.3.11",

Reproduction steps

See https://stackblitz.com/edit/puuk1z-imn8wg?file=src%2FApp.vue,src%2FInputText.vue&startScript=dev

Version

Vue.js 3.x and vee-validate 4.x

What browsers are you seeing the problem on?

  • Firefox
  • Chrome
  • Safari
  • Microsoft Edge

Relevant log output

No response

Demo link

https://stackblitz.com/edit/puuk1z-imn8wg?file=src%2FApp.vue,src%2FInputText.vue&startScript=dev

Code of Conduct
@byronogis byronogis linked a pull request Aug 26, 2024 that will close this issue
Open
@byronogis
Copy link
Author

byronogis commented Aug 27, 2024 •
edited
Loading

I carefully checked the record of #3429. Maybe the above situation is an acquiescence behavior?

I am currently adding a optional props forceValuein to Component B for solve current issue.

// component B
// create a new field (by useField, and have a avaliable initialValue y)


const props = defienProps<{
  forceValue?: any
  // ...
}>()

const {
  value
} = useField('name', undefined, {
  initialValue: props.forceValue || 'y'
})

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(usefield): exist value will be covered when a initial value there byronogis/vee-validate
1 participant
@byronogis