Drop special behavior for `@Argument Map` in favor of doing the same via `@Arguments Map`

[MiguelAngelLV]

For me, are the same.

There any way to get the value directly in to the map?

For the request

mutation updateUser(input: { name: "updated" } )
mutation updateUser2(input: { name: "updated" } )

Actual

@MutationMapping
fun updateUser(@Argument input: Map<String, Any) {
    
    val name = input.get("input")?.get("name")

}


@MutationMapping
fun updateUser2(@Arguments input: Map<String, Any) {
       val name = input.get("input")?.get("name")
}

I see more logical this

@MutationMapping
fun updateUser(@Argument input: Map<String, Any) {
    
    val name = input.get("name")

}


@MutationMapping
fun updateUser2(@Arguments input: Map<String, Any) {
       val name = input.get("input")?.get("name")
}

[rstoyanchev]

@Argument was created earlier, and at the time this special case (Map method parameter + no annotation name attribute), was the main way to access the raw arguments map. After @Arguments was added to bind from the full map, you can now also use @Arguments Map for the same.

Now that @Arguments can be used to access the raw arguments map, I think it does make sense to remove this special case for @Argument and let it always use a name.

The main challenge is impact on existing applications. A controller that relies on existing behavior would now get null, and there is no way to know if the intent is to access the full map, or if the named argument is simply not present. Furthermore, the named argument could be present by coincidence (name overlap) in which case the controller would now get the sub-map for the argument instead of the full map. This is why we'll introduce this in 1.2.

[rstoyanchev]

Note that currently you can name the argument explicitly like so:

@MutationMapping
fun updateUser(@Argument("input") map: Map<String, Any) {   
    val name = map.get("name")
}

[MiguelAngelLV]

Note that currently you can name the argument explicitly like so:

@MutationMapping
fun updateUser(@Argument("input") map: Map<String, Any) {   
    val name = map.get("name")
}

When I add a name to argument with Map, it throws error.

    @MutationMapping
    fun updateUser(@Argument("user") input: Map<String, Any>): String {
       return "${input["name"]}"
    }

mutation {
  updateUser(user: {name:"test"})
}

type Query {
    getUsers: [User!]!
}

type Mutation {
    updateUser(user: UserInput!): String
}


input UserInput {
    name: String!
}

type User {
    username: String!
    name: String!
    lastName: String!
}

I get this error:

Field error in object 'map' on field '$': rejected value [null]; codes [unknownType.map,unknownType]; arguments []; default message [Unknown Map value type]

But, with this works

    @MutationMapping
    fun updateUser(@Argument input: Map<String, Any>): String {
        val user = input["user"] as Map<String, Any>
       return "${user["name"]}"
    }

The actual docs idicate that for Map the annotation must not have a name

https://docs.spring.io/spring-graphql/docs/current/reference/html/#controllers-schema-mapping-signature

The main challenge is impact on existing applications.

So, all Map arguments for existing applications don't have name, so, a "named argument" can be a backward compatible solutions.

[rstoyanchev]

This should work as I described, but it looks like we expect the Map to be declared as Map<String, Object> and reject Map<String, ?> because we can't differentiate if you want the raw map or a map of some typed objects. I think we can relax this a little to treat Map<String, ?> the same way as Map<String, Object>, so I've created #554. In the mean time, use Map<String, Object>.