AutoMoq
AutoMoq copied to clipboard
darrencauthon
Upgrade Unity?
My first thought is "no." This project is dependent on Unity, but under the hood. If I were to upgrade Unity, no user of AutoMoq today would be able to tell the difference. Plus... I think the latest versions of Unity have different methods to inject policies like the one that allows me to inject mock objects automatically.
However, upgrading to Unity will keep the project up-to-date with current standards. It would also give users of current versions of Unity the ability to use AutoMoq, as a dependency on a years-old version of Unity would be a dealbreaker.
The problem is that I know nothing about the latest version of Unity. The version of Unity in AutoMoq is one that I've used on dozens of projects, so I know it and I trust it. It works.
I tried upgrading Unity when I was setting up the latest version of AutoMoq, and I could not get it to work within an hour or two. Unity's new major version introduces breaking changes (which is to be expected), and I don't understand how to migrate this old behavior to the new system. Someone who knows the latest Unity might be able to make this migration in 15 minutes.
I'm going to wait for that person. That person might be me someday, should I need to use the latest Unity in an app. I just don't want to beat my head into a wall for hours trying to figure out the latest Unity abstractions.
To summarize:
If I get a pull request that has this Unity upgrade and all of the existing tests pass, I will release a new major release of AutoMoq.
@celluj34 Yes... but the tests won't write the code. :)
I tried some time ago to do this, but I was not able to make all of the tests pass. I gave it my best shot back then, and perhaps I could do better if I tried again... but it's been a time-suck to me.
I bet someone who had more experience with the newer version of Unity could take this on. I just don't know how the newer stuff works versus my ol' fav version of Unity. The one I went to battle with for many projects.