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.
While Player is strict about syntactically invalid expressions, it should still be allowed to execute them if the implementation desires. This change exposes the Expression Parser's
strict
attribute on the Expression Evaluator's hook to allow it to be set via theresolveOptions
hook. This change also changes the behavior around throwing those errors to only throw recoverable errors ifstrict
istrue
.Change Type (required)
Indicate the type of change your pull request is:
patch
minor
major
Release Notes
Expose Expression Parser's strictness option via the
resolveOptions
hook📦 Published PR as canary version:
0.7.2--canary.315.10130
Try this version out locally by upgrading relevant packages to 0.7.2--canary.315.10130
Version
Published prerelease version:
0.7.2-next.1
Changelog
Release Notes
Expression Parser Strictness (#315)
Expose Expression Parser's strictness option via the
resolveOptions
hook🐛 Bug Fix
Authors: 3