– Would it be possible to move the generation of AOTClasses.cs and link.xml to an automated build step, so you don’t have to manually trigger this?
– Would it even be possible to automatically detect which types are needed? What would it take to do that?
I can get behind both of these suggestions!
We’re experiencing the same workflow issue described here. I think it makes sense to auto import/export or auto save/load these typePrefs in such a way that they are part of the project.
I also agree that this would be great, but it could cause some annoying merge conflicts if two people add different types — unless the type format is something amendable to version control (.yaml?).
guyboots_thunderbro
