Questioning Plutus API design decision

Question

In Lecture 10 from the Plutus Pioneer Programm there is a replica of the Uniswap Smart Contract built on top of Plutus. It is actually part of the standard Plutus use cases Plutus Uniswap

To have a better user experience and to get to know it better i wanted to build a GUI around it. If you are interested you can find it in this github repo

Now to my question. What is the reason behind the design decision for the Status endpoint of the Plutus PAB Rest API. In order to read the funds we have first to call the funds Endpoint which returns nothing and secondly you have to call the status endpoint.

This is the Frontend Code from Lars where he reads the funds

This makes it very difficult if you want to have concurrent calls one for the funds and one for the pools

Why is there not a dedicated status endpoint for funds and pools?

Answer 1

The only way to read a state of the smart contract is using a contract instance status endpoint (api/contract/instance/$INSTANCE_ID/status). Other endpoints can only trigger a change of the state but they cannot return it so it's always a two step process.