Identify edge cases for custom messages in explain() #220
Description
Ah much clearer, I didn't know that method existed. Thanks!
Do you think we should account for [] here or make a new issue where we go through edge cases and write custom messages? I don't know if a path of [] will ever be passed.
I made an attempt in 3b03620, but we can roll back if it is too convoluted. It takes the current message of:
To something that makes at least a little bit more sense:
Originally posted by @joelostblom in #208 (comment)