You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, I am grateful for developing such a powerful and easy-to-use platform for AI tasks. It's been a tremendous help in my projects.
I've been using the JavaScript SDK to integrate Scale AI services into my application. While the SDK is intuitive and well-documented, I've noticed that it lacks several features in the Python SDK.
Is there a roadmap for achieving feature parity between the JavaScript and Python SDKs?
Maintaining SDKs for different languages is challenging, but bringing the JavaScript SDK to the same level as the Python SDK would benefit the community.
Are there plans for extending the functionality of the JavaScript SDK to match the Python SDK? If yes, is there an estimated timeline?
Thank you for taking the time to read my issue.
The text was updated successfully, but these errors were encountered:
Scale AI uses Fern to create their Node.js SDK automatically. Thanks for the request to match functionality between JS and Python. No estimated timeline right now, but I'll follow back up here as one is established by the Scale team.
Hello Scale AI Team,
First, I am grateful for developing such a powerful and easy-to-use platform for AI tasks. It's been a tremendous help in my projects.
I've been using the JavaScript SDK to integrate Scale AI services into my application. While the SDK is intuitive and well-documented, I've noticed that it lacks several features in the Python SDK.
Is there a roadmap for achieving feature parity between the JavaScript and Python SDKs?
Maintaining SDKs for different languages is challenging, but bringing the JavaScript SDK to the same level as the Python SDK would benefit the community.
Are there plans for extending the functionality of the JavaScript SDK to match the Python SDK? If yes, is there an estimated timeline?
Thank you for taking the time to read my issue.
The text was updated successfully, but these errors were encountered: