Matt Vague

Feature/node source location

1

I went ahead and implemented support for MathJS on [ASTExplorer](https://astexplorer.net) (see PR [here](https://github.com/fkling/astexplorer/pull/654)) but was unable to implement the source code highlighting feature since MathJS doesn't store positional information on...

`OperatorNode` type should accept generics for 'op' and 'fn'

3

# The Problem Right now all operator types share the same basic `OperatorNode` type. This has a few consequences: - Nothing right now prevents creating invalid operators (like I did...

Right now transform always return `MathNode`. Would be better if it returned the type returned by its callback

`calculateNecessaryParentheses` blows up cryptically when `getPrecedence` returns null

1

I accidentally created a node with the `fn` name `mult` instead of `multiply` i.e. `new OperatorNode('*', 'mult', [...])`, and when I went to tex-ify it I got the error `Cannot...

`transform` should accept and compose multiple transforms

1

Per discussion [here](https://github.com/josdejong/mathjs/discussions/2562), it would be great to be able to pass multiple transforms to the `transform` function and have them be composed e.g. ```js myNode.transform(transform1, transform2) myNode.transform([transform1, transform2]) ```...

`gcd()` should accept array

6

I would expect `math.gcd([1,2])` to work the same as `math.gcd(1,2)` however it currently throws "Too few arguments in function gcd (expected: number or BigNumber or Array or Matrix or Fraction...

Forgive me if I missed it, but couldn't see instructions for the right place for feature requests/proposals. Just going to leave this here for now but feel free to point...

Patch missing TextEncoder/TextDecoder

1

window.TextEncoder and window.TextDecoder are standard browser features not supported by JSDOM but which React 18 [now requires](https://github.com/facebook/react/blob/e09518e5bbb78447d6c86481cf0dcafb4b09c734/packages/react-server/src/ReactServerStreamConfigBrowser.js#L107). This PR patches those with the [node implementation](https://nodejs.org/api/util.html#class-utiltextencoder) Cheers!

Returning undefined from treeWalker throws error

2

Hey there, looks like currently `Tree.tsx` assumes that treeWalker will always yield valid node data and that it will never be undefined, even though that is a valid return value...

It seems that the FixedSizeTree example in the readme doesn't work because it expects all nodes to have children which they don't. Wasn't sure though if if the right solution...