Brendan Zabarauskas

I'm now wondering if we could investigate a richer 'diagnostic tree'. Perhaps something like: ```rust Diagnostic::error() FileLabel::primary(file_id, range) FileLabel::secondary(file_id, range) FileLabel::secondary(file_id, range) FileDiagnostic::error(file_id) Label::primary(range) Label::secondary(range) FileLabel::secondary(file_id, range) ``` I'm unsure...

This does seem like something tools should expose, kind of like the coloring of output - something like `--wrap-lines auto|never|width=INT`. This is an issue for tools like CI that don't...

Similarly to [my comment in #248](https://github.com/brendanzab/codespan/issues/248#issuecomment-647090091), I'd probably recommend making a custom implementation of `codespan_reporting::Files` if you're running into these kinds of limitations. My long term plan is to deprecate...

ahhhh - yeah I'm not sure! One idea we had was to have an lsp backend for the `codespan_reporting::Files` trait: #227 - maybe this would be sort of what you...

I wonder how much this is related to #187? 🤔

It might be helpful to give a mock-up of what you want the output to look like as well! Might be easier for me to visualise that way.

This is similar to #125, but for the horizontal case. I think rustc does this currently - it might be useful to look at the test cases to see some...

Thanks for your issue! I've been trying hard to de-emphasise `codespan`, and emphasizing `codespan-reporting`, because I've found it rather challenging to create a one-size-fits all thing for handling files. This...

Ohhh, that is a good idea, yes! Now I have a better handle on the `lsp-types` version ranges this could also be helpful too - it was a constant pain...

I'd definitely be open to collaborating on this! Feel free to chat on [Gitter](https://gitter.im/codespan-rs/Lobby) or the the #langdev channel on the rust community discord if you like!