json-formula

json-formula copied to clipboard

Make string to number coercion more strict

4

The last number of changes to json-formula have been trending toward being more strict wrt parameter handling and coercions. We throw many more TypeErrors and ExecutionErrors than we used to....

JohnBrinkman

Welcome to [Renovate](https://redirect.github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable...

renovate[bot]

Example of how to add a custom function with signature using constants

1

Hi there, I need to add a custom function to the JSONFormula instance. While I have been able to define and add the function, I'm having trouble specifying the data...

VentuzVictorPerez

Looks like spaces at the end count as the fractional part, which ruins the result: `toNumber("070.070", 8) -> 56.109375` `toNumber("070.070 ", 8) -> 56.013671875` `toNumber("070.070 ", 8) -> 56.001708984375` `toNumber("0F0.0F0",...

Eswcvlad

Undocumented type behavior for hidden properties in `value` and `hasProperty`

1

Currently in the implementation of `value` and `hasProperty`, if there is a hidden property `name` in `obj`, type checking of arguments is ignored. This is codified in these tests: -...

Eswcvlad

String to number conversion corner cases

6

When implementing the spec, I assumed, that for a string to coerce to a number it should, basically, contain a number literal per json-formula rules. But it looks like in...

Eswcvlad

Leading zeros in number literals.

2

It looks like in the implementation it allows number literals to have leading zeros (i.e. `09` results in `9`). This is valid per the grammar in the spec, but it...

Eswcvlad

Calling registered functions with 0 arguments.

1

Currently in the spec: > The registered function may take one parameter. It is pretty clear, that it would be implemented by just evaluating the expression with the argument as...

Eswcvlad