Reduce clippy noise from #[Object] macro

[negezor]

At the moment, when I run cargo clippy, I get a huge number of warnings related to “this function has too many arguments”. This mainly happens in fields that have a large number of filters or relay connections.

warning: this function has too many arguments (9/7)
   --> src/graphql/schema/users/user_friend.rs:116:1
    |
116 | #[Object]
    | ^^^^^^^^^
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_many_arguments
    = note: this warning originates in the attribute macro `Object` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: this function has too many arguments (11/7)
   --> src/graphql/schema/users/user_log.rs:506:1
    |
506 | #[Object]
    | ^^^^^^^^^
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_many_arguments
    = note: this warning originates in the attribute macro `Object` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: this function has too many arguments (8/7)
   --> src/graphql/schema/users/user.rs:644:1
    |
644 | #[Object]
    | ^^^^^^^^^
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#too_many_arguments
    = note: this warning originates in the attribute macro `Object` (in Nightly builds, run with -Z macro-backtrace for more info)

Description of the feature

I suggest adding the following snippet for clippy if the method has more than 4 arguments.

#[allow(clippy::too_many_arguments)]

[sunli829]

what version of Rust are you using?

[negezor]

@sunli829 These warrnings are present in several major versions of async-graphql. I just tried not to pay attention to them until the project grew.

async-graphql: 7.0.3
rust: 1.77.0