-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
💅 Implement a handler based on grace #107
Comments
Hey 👋 Grace's current repository can be found here: https://github.com/johnyob/grace. I'd recommend that asai doesn't use grace until early 2024 as I'm still (albeit slowly) working on grace's renderer. |
@johnyob Thanks for the link---I just updated it. If you are worried about the unstable API, asai is also very experimental. 😅 Also the core asai package will not depend on |
@johnyob Hi, I realized that you are using the package |
Yes, in the initial release of |
@johnyob I am glad that it's now ready! This issue is no longer blocked. |
@johnyob I believe the only things to do are
Here are some details:
I feel the other direction is also straightforward, except that Grace allows multiple primary labels. I wonder if I missed anything... |
@johnyob Question: an asai diagnostic comes with a stack backtrace. Should them be "secondary" labels, or standalone diagnostics by themselves? |
@johnyob Hi, I wonder if you think Grace is stable enough now, and whether you have any comment about the questions I asked above? (Sorry for the bothering but I am very interested in implementing the handler.) |
@johnyob has implemented the Rust-style diagnostic rendering at
https://gitlab.com/alistair.obrien/gracehttps://github.com/johnyob/grace.On the surface, it looks straightforward to adapt it into an asai diagnostic handler. Of course, the renderer will not satisfy our Level-2 display stability requirements, but I think we can implement a renderer with lower display stability requirements, which has the benefits of not relying solely on colors to highlight spans.
The text was updated successfully, but these errors were encountered: