-
Notifications
You must be signed in to change notification settings - Fork 550
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
Lint failed on source #340
Comments
This comment has been minimized.
This comment has been minimized.
Some developers may skip the lint step, could you please help to setup the lint Action? |
@juzhiyuan I think I can open a PR to fix most of the warnings. But the big question is how to refactor the name convention like foo_bar. I will open a PR soon to do what I can do, and then leave the important issues about refactor to the core teams.
Once lint is set up, PR that failed the lint test couldn't be merged. So it can't be skipped in any way. |
I have fixed some lint errors. Here's what left:
What do you think of the naming?
|
Thanks, I need some time to have a conclusion here. |
After some conclusion, we decide to allow snake_case variable name due to some logics from API, welcome PR to enable this feature. |
We should fix these issues before any attempt to set up a linter on Actions.
The text was updated successfully, but these errors were encountered: