When Magento's generated interceptor classes don't match your constructor changes, you get type errors. The generated code directory is temporary in developer mode and must be rebuilt in production with the DI compile command. Delete and regenerate it to fix mismatches.
bin/magento setup:di:compile
In Magento when we inject dependencies in the constructors, we may run into odd errors from time to time that complain about there being a type error when creating an object. This won't make much sense to you because the constructor in local classes will appear just fine, but this error stems from generated code that was placed in the generated code directory. If we open up the related file for this class in this directory, you'll notice an interceptor at this location. This file was created by Magento to add functionality to our code. Since we changed the constructor dependencies from this class, it no longer matches the generated code, which creates a mismatch. Now the data within this generated code directory is ephemeral, meaning it can go away at any time. This means that we can remove and rebuild the contents of it whenever we wish. In developer mode, if these files don't exist, they are created on the fly at runtime in production mode. These files are not dynamically created for us for performance reasons, but can easily be created with the Bin Magento setup di compile command.
