Fix handling of scenario when attribute name is the same as function name (e.g. "mean(mean)") #911
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.
https://www.pivotaltracker.com/story/show/186152786
mean(mean)
is a valid formula, but it used to crash in V3. I realized this would be a problem when I added theisNonFunctionSymbolNode
helper as part of the previous PR. This is all due to how MathJS parses expressions (function node + separate function name node).I also renamed
canonicalizeExpression
todisplayToCanonical
, so it's the inverse ofcanonicalToDisplay
.Additionally, I've added quite a few unit tests that also cover the scenario that caused a real-life bug discussed above and in the PT story.