@bx80 We maybe should stop trying to support incorrectly provided parameters. The action name is meant to be passed as a string. We do not expect it to be an array. With Matomo 5 we introduced the possibility to typehint API parameters. So we could simply add a typehint to all of the API methods that expect action name or type to be a string. If a user provides it as an array the API should then give a proper error message.

Since we do have parameters elsewhere that do accept multiple types it's hard to know exactly what should be allowed where. Moving to type hints wherever possible will be a good way to solve this and add some certainty, though it might expose a few bugs on the way!

I'll adjust this PR to simply add type hints and use that approach for any similar issues. 👍

@bx80 we added a lot code in the past to handle incorrectly provided parameters as there was no easier way to do it and we wanted to avoid php errors to be thrown. But using the new typehints possibility makes it a lot simpler, as the API will directly return a proper error and we might actually be able to get rid of a lot error handling code in the APIs over time.