-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Lots of compiler warnings #677
Comments
Yes, it would be good👍 But it is very desirable to do it through setting |
And fix these errors. For ShapeCrawler#677
"The field '{field}' is never used" And fix these errors. For ShapeCrawler#677
"unreachable code detected" And fix these errors. For ShapeCrawler#677
"The variable is assigned but its value is never used" And fix these errors. For ShapeCrawler#677
"XML comment has a param tag for '{param}', but there is no parameter by that name" And fix these errors. For ShapeCrawler#677
"Nullable value type may be null" And fix these errors. Question: Would it be better to update the public API to not allow user to send in a null, given that AddAHighlight won't accept null. For ShapeCrawler#677
"The variable '{variable}' is declared but never used" And fix these errors. For ShapeCrawler#677
@jcoliz Is this issue still open, Can I start working on it ? |
@yogendrasgautam, thank you for the interest. Yes, the issue is open. There are still warnings left. |
@ashahabov thanks for confirmation. Will take a look into it |
@ashahabov @yogendrasgautam Fascinating! Which warnings? It's clean for me...
|
Ok, nevermind, I see them! They only come up in release configuration. 96 warnings cluttering up my release pipeline 😄 |
@ashahabov Compiling generates many warnings. Would you take a PR to clean these up?
The text was updated successfully, but these errors were encountered: