he/him 
Rome produces diagnostics, a way to represent problems in your code. These are passed around, concatenated, deduped, they can come from a variety of sources.
Show this thread
Rome has categories for a diagnostic, the same way eslint will tell you what rule an error came from. But that's not enough when there's a lot of indirection. An error came from the linter, but why was it being invoked in the first place? etc
-
-
So I added a --verbose-diagnostics flag, and propagated a reason for processing every time diagnostics go through a layer of indirection. Thus giving you a complete path. It appears at the bottom of a diagnostic with a "Why are you seeing this diagnostic" section:pic.twitter.com/1tYmwxNDtN
Show this thread -
(To clarify, the "why are you seeing this" section only appears with the --verbose-diagnostics flag. No point in showing it by default)
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.