Right now, validation happens on set. Moving this to get would make sure that if another component updates the value, the validation for the first component still runs. This might or might not be desired behavior.
If you are editing a value and it fails the validation for a different control, this may not be good. If it fixes a validation, this is probably good.
We could make it so that the validation runs on get, and if it succeeds, set the validation, but if it fails, dont.
Right now, validation happens on set. Moving this to get would make sure that if another component updates the value, the validation for the first component still runs. This might or might not be desired behavior.
If you are editing a value and it fails the validation for a different control, this may not be good. If it fixes a validation, this is probably good.
We could make it so that the validation runs on get, and if it succeeds, set the validation, but if it fails, dont.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Right now, validation happens on set. Moving this to get would make sure that if another component updates the value, the validation for the first component still runs. This might or might not be desired behavior.
If you are editing a value and it fails the validation for a different control, this may not be good. If it fixes a validation, this is probably good.
We could make it so that the validation runs on get, and if it succeeds, set the validation, but if it fails, dont.
Validation now runs on get, only updating on success. This way you can fix the validation for one component by updating a different one.