3rd party or builtin interfaces may have methods requiring several arguments (e.g. Xamarin.Forms.IValueConverter, which defines Convert and ConvertBack with four arguments each). In these cases, CleanCode should not warn that the methods that implement the interfaces require too many arguments.
In general, I suggest that interface-implementing methods should be skipped entirely by the "too many arguments" check, and instead CleanCode should warn about this on the actual interface definitions.
3rd party or builtin interfaces may have methods requiring several arguments (e.g.
Xamarin.Forms.IValueConverter, which definesConvertandConvertBackwith four arguments each). In these cases, CleanCode should not warn that the methods that implement the interfaces require too many arguments.In general, I suggest that interface-implementing methods should be skipped entirely by the "too many arguments" check, and instead CleanCode should warn about this on the actual interface definitions.