Skip to content
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

Different severity levels for code diagnostics #14

Open
Eugleo opened this issue May 1, 2020 · 4 comments
Open

Different severity levels for code diagnostics #14

Eugleo opened this issue May 1, 2020 · 4 comments

Comments

@Eugleo
Copy link

Eugleo commented May 1, 2020

Currently, all of the code diagnostics are of the lowest level, hint. It would be helpful to split them into error/warning/info. Is this a design decision, or just a temporary one?

@jeapostrophe
Copy link
Owner

jeapostrophe commented May 1, 2020 via email

@Eugleo
Copy link
Author

Eugleo commented May 1, 2020

That's good to hear. Looks like something a beginner like me could handle. I guess you'd like to stick to DrRacket's behaviour here as well. Is there any documented list of DrRacket's warnings/errors that we could use?

@jeapostrophe
Copy link
Owner

jeapostrophe commented May 1, 2020 via email

@cfinegan
Copy link
Collaborator

This issue is at least partially resolved by commit 61a7511. Reader and syntax errors are no longer reported as hints. There may be other DrRacket notifications that we're not displaying, so I'm leaving this open for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants