When a consequence sets a property with a value that is numeric, use setInteger #1478
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.
(\d+)
. A handful of them have([d,]+)
.In particular:
I notice that the last two are in [], which means they are evaluated as a ModifierExpression.
One of them uses "stripcommas" and the other does not.
The first three are simply stored as parsed.
That confused several programmers, one of whom declared that "it is in the contract of Preferences that a numeric property's value has no commas". Bold statement, and not true, to my knowledge, but, whatever. We can do it that way to make JS coders happier.
This PR will look at the (evaluated) value and if it isNumeric (defined as "an integer, possibly with commas"), parse it as an integer (which strips commas), and store as an integer. If you later retrieve it as a String, there will be no commas.