Skip to content

Conversation

@TuTiDore
Copy link
Contributor

@TuTiDore TuTiDore commented Dec 23, 2025

Was able to fix some issues with v1 endpoints using "[]" or "`1" in name. Also needed to break apart 1/devices/pair/{pairId} because it was getting the same operationId

I'm able to generate with no errors off localhost. There are still some minor differences with v1 nullability, using Byte some places instead of number, and moving things around inside generated files. But overall seems to be pretty close.

Not sure why branching off has that duplicated commit. Maybe because It was draft / not directly merged? idk

@hhvrc
Copy link
Contributor

hhvrc commented Dec 23, 2025

Maybe we should just exclude the deprecated endpoint from api docs completely, and maybe do so with every v2 api that is meant to replace a v1 api, not sure 🤔

@TuTiDore
Copy link
Contributor Author

TuTiDore commented Dec 23, 2025

Maybe we should just exclude the deprecated endpoint from api docs completely, and maybe do so with every v2 api that is meant to replace a v1 api, not sure 🤔

There was only that one endpoint that was messing up the ts-client generate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants