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
-
-
Show this thread
-
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 -
-
-
Is there anywhere to read about Rome? I keep seeing you mention it and it sounds interesting but I don't know what it is. It's still a WIP right?
-
Yeah it's WIP. Doubt it will be open sourced until, at a minimum, end of the year. https://twitter.com/sebmck/status/1108407803545214977 … are a good summary. Publicly tweeting is a good way to get early feedback and keep myself motivated.
- 1 more reply
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.
he/him 