parameter type mismatch checking + improvements to ParameterType.SELECT
#3557
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.
trials will now properly check if non-array parameters given are of the same type, throwing a warning if not in order to give more helpful message as opposed to some variation of some method being called on a mismatched type not existing. along with this,
ParameterType.SELECTnow properly checks if the value given is in theoptionsfield; plugin developers may now specify certain possible parameter values for a parameter removing the need for manual parameter input validation.originally was going to be an error, but this would technically constitute as a breaking change and break some pre-existing setups (see: #3556). to prevent other experiments that import our stuff through unpkg, we'll just make a it a warn and target erroring on mismatch for v9.