Feature Request: Add `GET` portion to new HTTP api about companion HOT 2 OPEN

Incidentally I did reach out to Irisdown who suggested they might make a modification to RSC to support POST requests. This would solve the second use case I posted, but not the first.

from companion.

There isn't a deadline because there isn't a well defined plan in what will be in each Companion release, its gets decided based on what gets done. I can say that I won't be removing this stuff in 3.3, and I probably wont in 3.4. Tbh there is no compelling reason to remove it yet, so it could well end up staying for multiple releases.

Changing GET to POST wasn't the main motivator for the api change, that was driven by needing to support the page/row/column syntax, and the opportunity was taken to also conform properly to REST principles.
So the old api won't be reinstated, but a new GET portion could be added to the new api to allow for your use cases. I am tempted to say it should be disabled by default as its use should be discouraged (doing a POST should be preferred when possible)

from companion.