[ ] Add unbalanced parenthesis check and in original FRQ, or other error checks. FYI, usually when structuring code with error checking it can greatly impact code structure.
[ ] Build in Power of operator ^:2 ^ 1 = 2, 2 ^ 2 = 4, 2 ^ 3 = 83. Build an API to receive an expression and respond with a result. This is a good opportunity to respond with an error if you built in parenthesis or other error checking.
see rpnToResult
Advanced. Deeper parsing and evaluation.
[ ] Try adding single argument function SQRT. This should be combined with ()'s to make sense, SQRT(expression). Though "SQRT 1" could work.
Advanced. Deployment and Frontend.
[ ] Deploy all of your APIs to Team Backend repo.
[ ] Start making Frontend pages to interact with APIs.
[ ] Finish rpnToResult for Calculator![image](https://user-images.githubusercontent.com/73082021/205709542-44243a3c-5b3c-486a-b590-dd70f36c4a82.png)
[ ] Add unbalanced parenthesis check and in original FRQ, or other error checks. FYI, usually when structuring code with error checking it can greatly impact code structure.![image](https://user-images.githubusercontent.com/73082021/205709656-4252463a-aca8-4bd3-9f38-fa554595b72e.png)
[ ] Build in Power of operator ^:2 ^ 1 = 2, 2 ^ 2 = 4, 2 ^ 3 = 83. Build an API to receive an expression and respond with a result. This is a good opportunity to respond with an error if you built in parenthesis or other error checking. see rpnToResult
Advanced. Deeper parsing and evaluation.
Advanced. Deployment and Frontend.
[ ] Deploy all of your APIs to Team Backend repo.![image](https://user-images.githubusercontent.com/73082021/205709820-519d582c-6aa8-4abb-abd2-5788d9f9472c.png)
[ ] Start making Frontend pages to interact with APIs.![image](https://user-images.githubusercontent.com/73082021/205709947-c2c5bf7d-5478-4e65-bb10-9601aa94eee9.png)