Skip to content

Linter #325

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

Merged
merged 1 commit into from
Aug 13, 2020
Merged

Linter #325

merged 1 commit into from
Aug 13, 2020

Conversation

sbarzowski
Copy link
Collaborator

No description provided.

@sbarzowski
Copy link
Collaborator Author

Some cleanup is still needed, but it's functional. At this point it may be worth looking at the examples and overall structure.

Later, I will provide more some explanation, rebase and fix the remaining issues (at least the important ones).

I may also split off a few changes from it (some things were needed to get it working, but are not strictly related). I've already done that with #318.

@sbarzowski
Copy link
Collaborator Author

I fixed the most important remaining issues and refactored it a little bit. I'll look at it a few more times, but I expect to merge it in a few days.

@sbarzowski sbarzowski changed the title [DNM] linter Linter Aug 12, 2020
@sbarzowski sbarzowski force-pushed the linter4 branch 2 times, most recently from 2e58f42 to 2ddee18 Compare August 13, 2020 18:17
@coveralls
Copy link

coveralls commented Aug 13, 2020

Coverage Status

Coverage increased (+0.3%) to 77.156% when pulling 8899c64 on sbarzowski:linter4 into 2e346e5 on google:master.

@sbarzowski sbarzowski force-pushed the linter4 branch 3 times, most recently from cd22d46 to 76c73d7 Compare August 13, 2020 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants