- Issue created by @godotislate
- 🇬🇧United Kingdom joachim
Does something for this need to be added to the core BC policy too?
- 🇬🇧United Kingdom catch
Once it exists we should add to the 'how to deprecate' page. For me this is a nicety that doesn't change the BC policy for forms though - there are plenty of form changes that would not be able to use this and we don't want to preclude ourselves from doing them. I also don't think we'd bother using this on obscure admin forms either.
- 🇳🇿New Zealand quietone
I agree with catch. Adding tag and item to the remaining tasks about updating the 'how to'.
Another thing to consider whether it's worth covering for the deprecation: Some form submit methods use
$form_state->getValues()
, then reference a specific key on the array, e.g.$form_state->getValues()['confirm'];
or$values = $form_state->getValues(); $confirm = $values['confirm'];
.MR is ready.
Can't trigger deprecations for usages of
getValues()
after all, so focusing strictly ongetValue()
.