Will be great a default option skipQueue: true

I mean all mutation skip Queue, unless option skipQueue: false.

I developing an app where most of the mutation does no need to be in a queue, just some few.

Will be event better if we can name queues.

In my case my problem is when you are updating the same record (it need to be in a queue)
but if the system is updating several records several times at the barely the same time, will be great have different queues for each record.

Thanks for your time

Review the existing mutation queue API and how skipQueue is represented before deciding how a default of true and named queues should interact. Done should include a clear behavior for queued and non-queued mutations, including updates to the same record and updates to different records.

Written by the indexing model from the issue text.