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
Describe the feature or improvement you're requesting
Since the library has been designed for Livebook usage, it's primary use-case is interactive. If something doesn't work when a cell is evaluated, one can look at the returned json in the output and manually fix whatever is wrong with the request. The returned JSON is usually pretty clear about what went wrong.
This has worked well for my usage, but I'd like to support non-interactive usage for those who convert their livebook samples to libraries / apps that run non-interactively.
This might involve throwing / raising errors whenever the API returns an error message. Or returning an :error tuple (requiring a change at the point of call). My preference would be to mimic what the official python library does
Please upvote this if you this is something you need for your use case. Leave a comment if you have an opinion on how it should be handled.
The text was updated successfully, but these errors were encountered:
Describe the feature or improvement you're requesting
Since the library has been designed for Livebook usage, it's primary use-case is interactive. If something doesn't work when a cell is evaluated, one can look at the returned json in the output and manually fix whatever is wrong with the request. The returned JSON is usually pretty clear about what went wrong.
This has worked well for my usage, but I'd like to support non-interactive usage for those who convert their livebook samples to libraries / apps that run non-interactively.
This might involve throwing / raising errors whenever the API returns an error message. Or returning an
:error
tuple (requiring a change at the point of call). My preference would be to mimic what the official python library doesPlease upvote this if you this is something you need for your use case. Leave a comment if you have an opinion on how it should be handled.
The text was updated successfully, but these errors were encountered: