Allow past/future in ExprLevel via default value #8295
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.
Problem
ExprLevel supported past/future values if the default player was used. However, the pattern did not allow the default player, preventing the use of past/future values.
Solution
Used registerDefault instead of register. Improved code quality, added example, added an extra check for changing past/future values in a level change event.
Testing Completed
Manual testing confirmed.
Supporting Information
Completes: none
Related: none