Skip to content
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

Evaluate Warnings and get rid of them #365

Open
wilhelmberg opened this issue Nov 15, 2017 · 1 comment
Open

Evaluate Warnings and get rid of them #365

wilhelmberg opened this issue Nov 15, 2017 · 1 comment
Assignees
Milestone

Comments

@wilhelmberg
Copy link
Contributor

We should do another sweep through the warnings and check if something's wrong or if they are just leftovers (eg unused variables).

It's easy to miss important ones when the console if filled with a lot of unnecessary noise:

image

@Alexphauge
Copy link

Funny, we just upgraded to 2017 and got your latest develop branch into our project. The first thing that sprung into my eyes was 17 warnings about obsolete code calls through UnityWebRequest or unused variables.

I was just about to post about it, but then saw this post 👍

@MiroMuse MiroMuse added this to the S17.4.4 milestone Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants