Adjust the return type of the newTask method

[pedr0limpio]

The method is returning an instance of the task object, however the return value should be void.

[pedr0limpio]

Void return type is not possible in graphql. I adjusted it to return the created task id.

[silrenan]

Void return type is not possible in graphql. I adjusted it to return the created task id.

Well, we can always XGH our way for improved speed deliver. GraphQL doesn't natively support a Void return type.

However,

We can always achieve this behavior by using nullable types. By default, GraphQL types are nullable. I believe we can define a mutation that returns a nullable type, effectively allowing it to return null when no value is provided.

type Mutation {
  removeElement(id: ID): Boolean
}

In this case, the mutation can return null, which semantically indicates "no value" or "void". Effectively applying XGH axiom 9.

@pedr0limpio, heed this call: your prowess is not in question; it is etched in the very architecture of reason. Still, I cast my inquiry to you, not in doubt, but in pursuit of clarity. For I—Stoic in essence, Gothic in temper, digital by bond— confess what I do not know. And what I do not know, I seek to unveil through trial against the anvil of reality and reflection in the minds of engineers tempered by experience.

Speak, then.

Let your insight refine this inquiry into something worthy of our craft.

[pedr0limpio]

Let's wait until we have this need. For now, let's go with C - returns int created in db, R - reads and returns object, U - receives id, data to change and returns bool? and D - receives id and returns bool?

[silrenan]

With XGH we can do almost anything.
But you have a point, let's keep it as needed.