[RiskIsAFriend]

Thanks for taking a look. On load there's instances where numbers aren't yet being calculated which gives some text reading "(invalid date)" and "NaN" in the place of results.

It's only when you fill out the "Current situation" inputs that the request to the API fires to run the calculations and return the results - I suspect the case here may be that the request hasn't been fired yet as the inputs haven't been fully filled?

I'll be working to make this user journey more clear in any case

[breck]

> that the request to the API fires to run the calculations and return the results

Why use an API? seems like that raises a lot of security/privacy issues and these calculations are simple enough to do locally, no?

[RiskIsAFriend]

Primarily because C# is my main language and I vastly prefer to write calculation engines with it.. Also the inputs could just as likely be random theoretical numbers, I am not perceiving a security or privacy issue?