We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The export of Error types would make it possible to catch raised errors and handle them accordingly.
An import of the errors like
from foundry_dev_tools import DatasetHasOpenTransactionError try: # something except DatasetHasOpenTransactionError as e: # something else except: # whatever
would be great.
from foundry_dev_tools import Errors try: # something except Errors.DatasetHasOpenTransactionError as e: # something else except: # whatever
I
The text was updated successfully, but these errors were encountered:
I think it's possible to import them via:
from foundry_dev_tools.foundry_api_client import DatasetHasOpenTransactionError
Nevertheless, I agree that this needs another solution.
Personally, I think the second approach is better because the top-level module will otherwise become too cluttered.
Will have a look at it tomorrow!
Sorry, something went wrong.
@jonas-w thanks, this works as a workaround 😀
@KochC are you still interested in contributing?
@jonas-w working on a first draft already 😉
Successfully merging a pull request may close this issue.
Issue checklist
Feature use case
The export of Error types would make it possible to catch raised errors and handle them accordingly.
Description of the Feature
An import of the errors like
would be great.
Alternatives you considered
An import of the errors like
would be great.
Additional Context
I
The text was updated successfully, but these errors were encountered: