Skip to content

Conversation

@igorwastaken
Copy link

@igorwastaken igorwastaken commented Jan 4, 2026

I created this endpoint in this SDK, if it's necessary to include it in the package.

Copy link

@velddev velddev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution! It would be ideal to move the v1 api endpoints to a seperate class or instance than the legacy API since it is not compatible on a lot of areas.

Aside from that, could you please revert the husky stuff? I don't think we use it as of right now and this shouldn't be randomly added to the repository.

@igorwastaken igorwastaken marked this pull request as draft January 5, 2026 02:22
@igorwastaken
Copy link
Author

I'll do some changes and add the new ApiV1 class, and separate it from Legacy Api class.

@igorwastaken igorwastaken changed the title feat: add endpoint: /v1/projects/@me/commands feat: add V1 endpoints to SDK Jan 5, 2026
@igorwastaken igorwastaken changed the title feat: add V1 endpoints to SDK feat: add v1 endpoints to sdk Jan 5, 2026
@igorwastaken
Copy link
Author

@null8626 is already doing this at #92

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