Skip to content
This repository has been archived by the owner on Oct 26, 2018. It is now read-only.

Provide context in error messages #55

Closed
ryanbrandenburg opened this issue Nov 3, 2016 · 4 comments
Closed

Provide context in error messages #55

ryanbrandenburg opened this issue Nov 3, 2016 · 4 comments
Assignees
Milestone

Comments

@ryanbrandenburg
Copy link
Contributor

As mentionaed in #53 there isn't enough context in error messages like this to make diagnosing issues easy. Let's see about piping through some information like what method was trying to be called.

@Eilon
Copy link
Member

Eilon commented Nov 4, 2016

Is this doable in 1.1.0? Or postpone 'til later?

@rynowak
Copy link
Member

rynowak commented Nov 4, 2016

We could probably wait for feedback on this one if it's hard. I just noticed it while debugging the #53 that error message isn't really helpful unless you know where to look already.

@Eilon
Copy link
Member

Eilon commented Nov 4, 2016

Let's try to fix in 1.1.0, but if we can't, we can move it out.

@ryanbrandenburg
Copy link
Contributor Author

This turned out to be faster than I thought due to using @rynowak's idea about nested exceptions. It's merged in now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants