giving access to `mathjs.import`

[Cube707]

Please fill out these Check-boxes

• I checked for existing similar feature requests
• I have read the docs and checked that the feature I am requesting is not already implemented
• My feature request consists of only one feature

Is your Feature Request related to a Problem or Annoyance?

It would be helpfull to define custom functions for mathjs, now I have some really long math-views that could benefit from defining custom functions

could use be clamp():

VIEW[min(max(0,{num}),10)][math]

manual formatting that should really be its own function:

VIEW[ concat(isPositive({memory^STR_mod})?'+':'', string({memory^STR_mod})) ][math]

Describe the Feature you'd like

I would like some way to get access to mathjs.import() (see docs). Either as a config or vie the js-api (similar to how itertools is exposed in js-engin or maybe as a API function?)

Alternatives

I can write JS-View and import my own js there, but they are always block element and not inline, which comes with its own set of annoyances.

Another alternative would be to make VIEW's back-referenceable, similar to how inline-buttons can be created from an invisible block button.

Additional Context

No response

[Cube707]

I will start to test this on my fork

[Cube707]

First finding: pre-filling the context object inside buildMathJscontext()

obsidian-meta-bind-plugin/packages/core/src/fields/viewFields/fields/MathVF.ts

Line 55 in e21434f

const context: Record<string, unknown> = {};

does indeed work as expected.

using the following declaration:

import { clamp } from 'packages/core/src/utils/Utils';

...

const context: Record<string, unknown> = {
	'clamp': clamp,
	'with_sign': function (num: number): String {
		if (num > 0) {
			return '+' + num.toString();
		}
		return num.toString();
	}
};

means the following test-document works as expected:

---
num: 12
---

```meta-bind
INPUT[slider(minValue(-5),maxValue(15)):num]
```

val: `VIEW[clamp({num}, 0, 10)][math]`

sign: `VIEW[with_sign({num})][math]`

---

not sure jet if a plugin wide math object or a plugin wide context object is the better approach

[Cube707]

creating a MathJsInstance and its functions importandcompile` also works great
as shown in Cube707@ab56a72