favonia

The first solution is exactly what you suggested: wrapping the TTY backend. The new type of diagnostics can be `('code, 'loctext) Diagnostic.t`. Then, the `map` function has a new type:...

@mikeshulman Yes. The current (incomplete) design for generic locations (that generalize text ranges) is: ```ocaml module type S = sig type t val to_range : t -> Range.t option val...

As we are breaking the interface with #184, maybe we should indeed hide the record type from the interface. And maybe the helper function could be `map_message` that takes the...

I think it's good to think about this issue when (re)designing locations and diagnostics (#184 and #169).

@schdief06 Hi, thanks for the reporting sorry for the trouble. What version of the updater are you using? There were reports about the mysterious 1034 errors a while ago (see...

On the other hand, maybe I should restore the FAQ about these 1034 errors in README.

> * We should rename `--yes` to something like `--accept-defaults`. It should be very clearly documented what this does (skips all prompts, push for private containers, may in the future...

Suggestion: can we put the ToS on https://oauth2.sigstore.dev/auth/device so that we can log in AND agree with the ToS at the same time?

@kentookura The API calls the [`emit` effect handler](https://redprl.org/asai/asai/Asai/Reporter/module-type-S/index.html#val-run) for each diagnostic, so you can intercept them and perform reordering or filtering. I'm happy to go back to the drawing board...

@kentookura The better design is to absorb what you plan to implement into the library. 😉