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.
Tator-JS bindings ended up being harder to use then
fetchCredentialsin 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 usingfetchCredentialsin new code.Tator-JS should be updated to alert developers of the deprecation status and avoid proliferating the usage of tator-js autogen bindings.