Tuple for routes

[oscartbeaumont]

I wonder if this formats better. Possible not so probs will be closed but just marking so I come back to it at some point.

t.router((
      admin_procedure().query("me", |ctx, arg: String| {
          println!("{:?}", ctx.user);
      }),
      admin_procedure().query("superSecretQuery", |ctx, arg: i32| {
          println!("{:?}", ctx.user);
      }),
      t.procedure().query("somePublicData", |ctx, arg: String| {
          println!("{:?}", ctx);
      }),
      // .openapi("/demo"),
      // library_scoped().query("demo", |library, arg: String| {
      //     // TODO
      // }),
  ))

[oscartbeaumont]

Brendan's idea:

fn main() {
    t.router()
        .procedure(admin_procedure().query("me", |ctx, arg: String| {
            println!("{:?}", ctx.user);
        }))
        .procedure(
            admin_procedure().query("superSecretQuery", |ctx, arg: i32| {
                println!("{:?}", ctx.user);
            }),
        )
        .procedure(t.procedure().query("somePublicData", |ctx, arg: String| {
            println!("{:?}", ctx);
        }))
        .procedures((
            admin_procedure().query("me", |ctx, arg: String| {
                println!("{:?}", ctx.user);
            }),
            admin_procedure().query("superSecretQuery", |ctx, arg: i32| {
                println!("{:?}", ctx.user);
            }),
            t.procedure().query("somePublicData", |ctx, arg: String| {
                println!("{:?}", ctx);
            }),
        ));
}

This would require the procedure key being stablised in rspc_core not rspc but in practice rspc_axum/etc will rely on it's format so i'm not sure this really changes anything.