-
Notifications
You must be signed in to change notification settings - Fork 230
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
Warnings again #796
Warnings again #796
Conversation
The lint changes are ready to be pushed but before doing that I noticed there are total
OK. I think this is because you work in a Windows environment and even the unmodified files come with a change since every lilne ends with So, please make sure the end of line character in your VS Code settings, |
@ebozduman This branch now builds and has the lowest warning setting enabled. It is ready to be merged and in new PR's I can set the warnings stricter. |
@ebozduman Can you run CI again? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
(Too many files make the review process very difficult and increases the chance of some unwanted changes to slip through inadvertently.)
* Fix more warnings * Nuget update * Extend interface * Move progres * Namespace changes * Format * Renames * Moves * More moves * More warnings * Use new package for reactive * Add editor config * Allow 0 * Fix warnings * Warnings as error * Lint changes * Revert "Drawingback Lint changes" This reverts commit ed1ba1b. * Fix lines * Add editor config update * More editor * More editorconfig * Format * Format * Format * Fixes * Format * Format * Runs bucket notification test by itself --------- Co-authored-by: Ersan Bozduman <ersanbozduman@gmail.com>
@ebozduman lots of file movements here to better structure the code and remove warnings. Can you help and add to this PR with fixes for the warnings? After this gets merged the analyzer can be enabled by default!