-
-
Notifications
You must be signed in to change notification settings - Fork 803
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
UniTask fails to compile when Physics or Physics2D module is disabled #222
Comments
I made PR which will fix this, but this issue also present for many other packages(Include unity official packages). |
I disagree with adding it to dependencies. |
I agree with @neuecc Probably conditional defines would be better |
Note that conditional defines doesn't work in Unity 2018.4. So it will be breaking changes for Unity2018.4 users. Package dependencies are supported in Unity 2018.4, so I used it, which makes no breaking changes for Unity 2018.4 users. Also, I previously tried to solve this kind of issue with conditional defines in #126, but it was not merged. I have not heard clear answer yet(I just heard that not desirable or disagree). |
This feature can be applied starting from Unity 2019.1 #if !UNITY_2019_1_OR_NEWER || UNITASK_PHYSICS_2D This shouldn't be a big deal since Unity 2018.4 will be out of support very soon https://unity3d.com/unity/qa/lts-releases
|
Personally, I agree with it.(So I made #126) I am ready to make PR with conditional define , but I'm really not sure about what @neuecc disagree and what will he agree. |
@Razenpok |
Thanks! |
As per title, you can disable built-in Unity modules which causes errors during compilation.
The text was updated successfully, but these errors were encountered: