I’m back on track building my complicated fee calculator, and as I worked through it, I found that it saved me a ton of extra work by adding conditional jump logic in the API calls (when applicable) to filter the the user to specific gambits based on previous choices. At first everything seemed to be working great, and then my round function through math.js stopped working. If I plug in a number that was generated through an equation exactly and test in the gambit console, it works, but when I reference the previous API calls total (exactly the same in this case) it fails to round and goes way wonky. The browser console reveals no errors while this is happening as well.
I had other instances too where a gambit would “spin” indefinitely, but once I removed the conditional jump logic, it would function. I know that it could easily have been user error, but the exact same conditional jump logic duplicated without an API call functions flawlessly. Maybe I’m just pushing the system too hard in what I’m asking it to do? I’m this close to making it work (it does work technically, but it seems pretty buggy). Any thoughts @vinit?