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

Proposal: add support for warnings #18

Open
per-samuelsson opened this issue Apr 4, 2017 · 0 comments
Open

Proposal: add support for warnings #18

per-samuelsson opened this issue Apr 4, 2017 · 0 comments

Comments

@per-samuelsson
Copy link
Contributor

That's something we wanted for long. I guess it's really about being able to introduce a code for anything, and then bind it to a severity level (i.e. warning, error).

Since we might want to change terminology of classes when doing that, I suppose we should do it at some point where we do other changes which will require us to update a big set of files in batch, like proposed Error.SCERRUPPERCASE => Error.ScErrPascalCase, and then do change maybe to Issue.ScErrWarningOrErrorOfSomeKind.

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

No branches or pull requests

1 participant