On 25/07/2023 04:09, Xintong Song wrote:
In this case, I wonder if it makes sense to bump the REST API version to
V2. That should allow us to gradually phase out the old APIs without the
above mentioned problems.
It's ultimately possible do do that; it just implies duplicating _a lot_
classes and setting up a class hierarchy between the messages such that
we don't need to duplicate all workers and slapping v2 onto all handlers.
It's quite a lot of monkey work really, with quite a maintenance cost on
the 1.x side.
Personally I'd like to avoid it; if we go with a v2 for this one all
other changes that I'm proposing will also be pushed into v2, which will
make the efforts more work and way harder to maintain in 1.x (and imo
the point of 2.0 is to be able to break things hard).
