Skip to content

Conversation

@st31ny
Copy link
Collaborator

@st31ny st31ny commented Oct 28, 2019

This addresses #71 and introduces a new ApiError exception type.

@st31ny st31ny changed the title #71 Use custom exception to signal a client error Oct 28, 2019
@bcb
Copy link
Member

bcb commented Oct 29, 2019

Thanks for submitting, it looks good, will take a closer look asap.

@bcb
Copy link
Member

bcb commented Oct 30, 2019

Need to update the documentation (the doc directory)

@st31ny
Copy link
Collaborator Author

st31ny commented Oct 30, 2019

Ok, I'll have a look at that, too.

@bcb
Copy link
Member

bcb commented Nov 1, 2019

Thanks @steinymity

Haven’t forgotten this, I have some time off work after today so I can give it a proper review.

@st31ny
Copy link
Collaborator Author

st31ny commented Nov 9, 2019

Are there any outstanding comments as suggested in #95? Github doesn't show me any in the code, though…

@bcb
Copy link
Member

bcb commented Nov 10, 2019

No they’re in this one, you should see them in pending status above?

@st31ny
Copy link
Collaborator Author

st31ny commented Nov 10, 2019

No, sorry, I can't see them. Even when looking at the commits or at the diff I cannot see any comment. Maybe I'm missing the rights to see them?

@bcb
Copy link
Member

bcb commented Nov 11, 2019

Sorry I had to submit the review!

@st31ny
Copy link
Collaborator Author

st31ny commented Nov 12, 2019

No worries , I just commented/resolved the issues.

* Allows methods to signal user-defined error condition.
@bcb bcb merged commit 8ad2068 into explodinglabs:master Nov 15, 2019
@st31ny st31ny deleted the i71 branch November 15, 2019 14:06
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

Successfully merging this pull request may close these issues.

2 participants