Chain operator execution order should be reversed

[Shan6305]

Currently, the chain operator executes guards last to first. For example, this code:

struct MessageGuard {
	message: String,
}
#[async_trait::async_trait]
impl Guard for MessageGuard {
	async fn check(&self, ctx: &async_graphql::Context<'_>) -> async_graphql::Result<()> {
		println!("{}", self.message.as_str());
		Ok(())
	}
}

pub struct Query;
#[Object]
impl Query {
	#[graphql(guard(
		chain(
			MessageGuard(message = r#""1""#),
			MessageGuard(message = r#""2""#),
			MessageGuard(message = r#""3""#),
			MessageGuard(message = r#""4""#),
			MessageGuard(message = r#""5""#),
		)
	))]
	async fn test(&self) -> String {
		"Test".into()
	}
}

would produce:

5
4
3
2
1

It would make more sense to execute guards from first to last. This would also match the behavior of the and guard, which executes guards from first to last. If there is some reason that this change can't/shouldn't be made, this behavior should at least be documented in the documentation.

[sunli829]

Released in v2.10.1