Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate tator-js bindings #1735

Open
bctcvai opened this issue Jun 20, 2024 · 0 comments
Open

Deprecate tator-js bindings #1735

bctcvai opened this issue Jun 20, 2024 · 0 comments

Comments

@bctcvai
Copy link
Member

bctcvai commented Jun 20, 2024

Tator-JS bindings ended up being harder to use then fetchCredentials in most use-cases. Due to the large number of dependencies brought in by tator-js bindings, the cost to maintain the tator-js bindings, and the lack of ability to integrate into complex workflows such as undo buffers it was determined to deprecate them in favor of using fetchCredentials in new code.

Tator-JS should be updated to alert developers of the deprecation status and avoid proliferating the usage of tator-js autogen bindings.

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

No branches or pull requests

1 participant