Guys, can we please have better documentation for the Management JS?
The a is lower case but in the spec it's Upper Case.
3 Replies
Hi House,
Thanks for bringing this up. I’ll discuss this with my team to review the inconsistency between the spec and the code. I’ll update you once we have more clarity.
Let me know if you come across any other issues in the meantime
Thanks for bringing this up. I’ll discuss this with my team to review the inconsistency between the spec and the code. I’ll update you once we have more clarity.
Let me know if you come across any other issues in the meantime
Theoretically shouldnt be too hard, the API page atm is rendered by the spec I guess? But it only has the API version not the JS version, all you guys gotta do is add this in. Yea I guess may be tricky to generate the right functino names for JS vs. HTTP methods. Anyway, hopefully this helps others cuz I got stomped on this for quite a bit lmao.
Hi House,
We've confirmed that this discrepancy is not an issue and won't affect your implementation. The method name you're seeing in the code is generated automatically by our code generation tool (
@hey-api/openapi-ts), which applies its own naming conventions based on best practices.
For your implementation, please use the method name as it appears in the generated codebase:addOrganizationUsers
Let us know if you need anything else or have further questions