Closed scarytom closed 5 years ago
I guess the proper fix for this issue is for yada to use a namespace qualified :status
keyword, which I believe is best practice these days, but that is a bigger change that is also API breaking.
I'll accept the PR, as it's binary compatible.
Yes, it's probably worth thinking about a proper way of communicating status via a ex-info using namespaced keywords, e.g. yada/status
.
No idea where this error originated from, but got an annoying exception from our prod system: