Question Active input handling from Both to Input System Package (New) and forbid the use of the old API

@Schubkraft mistakenly thought that when I changed from "Both" to "Input System Package (New)", Unity would stop referencing any assembly related to the old Input and get compiler errors on all the code that references that old API.

The reality is that it doesn't, so my question is: how can we introduce a mechanism to avoid that someone keeps using the old API if the active input handling is not in "Both"?

I see quite dangerous this behaviour because I imagine that the error will be a runtime error and this is something that is not easy to check/debug depending on the complexity of the project.

 

@Schubkraft I thought there was going to be some kind of compilation directive that at least adding it manually would make it not compile the old API but I see that not even that.

Well if you want developers and Asset Store publishers to switch to using the new API, this is not the way because wittingly or unwittingly, you can use (directly or indirectly) old API and not realize it.

 

While not compile errors, you'll get runtime errors (with stacks) from the old API when used with input setting set to "new".

 

But it is precisely the complex thing, it is not easy to detect runtime errors but it is easy to detect compilation errors.