The param userId is typed as type “User”, but the example shows passing a “number” type as this parameter. So if this method now accepts “User” type too and not just “number” like it always did, you should have it typed as a type union of “User | number”
Thanks for reaching out. This conflict seems to be due to the changes to User (announcement) that are currently in transition.
As far as I’m aware, numerical User IDs should still work as portrayed in the sample. I’ll work with the team to update the documentation descriptions to help point developers to announcement or existing guide article as this change rolls out.
Thanks again for flagging! Have a great rest of your week,
naahchos