-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Support additional lint levels beyond warning and error #149
Comments
We'll have to look into this. I started initially only supporting the two flags that loclist supports, |
Does the loclist really support only "E" and "W"? Related: neomake/neomake#584 |
I just had a look at
I guess by "etc." you can set other error types as long as you use a single character. |
Yep. |
I'd like to try implementing this. Should I just add support for info and message levels? |
Yeah, go for it. Some work will need to be done for each linter, where the different error levels are available, and some work will be needed for signs, the statusline, etc. |
Type |
I just pushed a commit so the status lines will continue to work if the other problem types are set. Now So the status functions should now tolerate the new problem types, and produce the current output. |
I pushed a commit for setting different syntax highlights for "info" items, style warnings, and style errors. Info and style warnings map to the highlights for warnings for now, and style errors map to the error highlights. |
Other types should be supported everywhere now. Individual linters will need to be updated to do something meaningful. Some better defaults can be set for highlights, etc., later. The new highlight groups have been documented. I'll think about a new statusline format, which will also fix #323. |
Some linters emit low-severity messages or additional information that is not considered a warning or an error. It would be useful to be able to represent these within ALE. For example, Neomake has 4 levels (error, warning, message, info).
The text was updated successfully, but these errors were encountered: