-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
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
located errors: database #124
Conversation
7d613da
to
a3549f3
Compare
cbc8ad5
to
b695309
Compare
This pull request is Ready to Review. |
b695309
to
9a3ba06
Compare
let details = format!( | ||
r#" | ||
status: ´{response_status}´ | ||
headers: ´{response_headers:?}´ | ||
text: ´"{response_text}"´"# | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey @da2ce7 , this is an interesting way to have a kind of "object literal" or "anonymous struct". It's related to #172
I would not include it in this PR unless we change all the asserts to follow the same pattern. Maybe the final solution could be a mix of this solution and what I proposed on that PR. In this solution, I still miss the error pointing to the origin line when the condition was not fulfilled.
I think this is a very helpful improvement. ack 9a3ba06 |
closing in favor of #178 |
Related Issue: #176
Depends #177
This is the first in a series of work to add locations to error messages. I have created the located_error.rs class that gathers location from the error call, and make use of it for the database errors.