Listen for removed inputs and unregister them #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses issue #66 by looping through the
MutationRecord
'sremovedNodes
array and removing entries for any validatable elements from the various state objects. This appears to fix the issue withisValid
andisFieldValid
for my test case, but there are a couple parts I'm unsure of:undefined
validators ingetFormValidationTask
which seems to indicate thatthis.formInputs[formUID]
still contains entries for removed inputs even though thesplice
call inuntrackFormInput
should have removed them.removed
boolean that's currently being passed toscan
and its children or to have a separate set of functions instead