-
Notifications
You must be signed in to change notification settings - Fork 57
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
[Pylint] override scoring to include info warnings #2813
Conversation
ooh perfect, thank you so much @l0lawrence, the CI is now failing which is good. Going to take a look at this later today |
Hi @msyyc, @tadelesh I think @iscai-msft is OOF, if you get a chance could you please take a look at the pylint warnings here? They are related to this issue:#2802 |
Sure. Now we are migrating some code to https://github.com/microsoft/typespec/tree/main/packages/http-client-python which has strict ETA so we will take a look after the migration done. |
The migration issue should also solve the pylint issues, since I fixed the pylint issues in the unbranded emitter. We have updated the branded emitter (the existing one we use to generate azure code) to depend fully on the unbranded emitter, so the code emitted by it should have the pylint issues solved. There is some issue with migrating the |
move to #2876 |
fixes #2802
default pylint scoring is:
(max(0, 0 if fatal else 10.0 - ((float(5 * error + warning + refactor + convention)/ statement) * 10)))
adding in
+info