fix: check potential variables for flyout variable fields #8873
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.
The basics
The details
Resolves
Fixes #8863
Proposed Changes
variableTypeswasundefinedin the constructor. The old test comments were incorrect and the test only passed because the test case block did not have asourceBlockproperty. The correct behavior is that passingundefinedbehaves the same as passingnull.nullsince that's what we say to do if you want to see all the variable types.setTypesmethod with the rest of the validation instead of thegetTypesmethod.@internalfromworkspace.getPotentialVariableMapsince it is called fromFieldVariablewhich may be subclassed.Reason for Changes
Test Coverage
Added tests and tested manually using the test block from the issue description
Documentation
Additional Information