CAUTION: I just took a look at the returned data and changed the spec to match that. It might still be possible that the api returns something different that doesn't match the patched spec.
Consulting the tables source code wasn't an option, as the wrong typing likely originates from it (no information to gain there).
I'm not sure how to move forward from here.
I don't have any confidence that the specs for that api are of any use. When something as fundamental as the typing of the row data is wrong, there are likely many more issues to be found. I dislike having to make a breaking release every time we try to fix it.
We might need to remove the tables client from the Nextcloud package again.
fixes: #2508
CAUTION: I just took a look at the returned data and changed the spec to match that. It might still be possible that the api returns something different that doesn't match the patched spec. Consulting the tables source code wasn't an option, as the wrong typing likely originates from it (no information to gain there).
I'm not sure how to move forward from here. I don't have any confidence that the specs for that api are of any use. When something as fundamental as the typing of the row data is wrong, there are likely many more issues to be found. I dislike having to make a breaking release every time we try to fix it. We might need to remove the tables client from the Nextcloud package again.