Make Update mutations backward compatible

Problem

I am SUPER frustrated that in 2.6.x, all of a sudden, the update syntax changed. This requires a major change to my entire client code base, and so i am simply not going to upgrade from 2.5.1 for a while.

Most of the time i just want to set a new value, esp for strings, so can we default to set.

Instead of passing down:

{
   field1: value,
   submodel: { 
      update: {
        subfield1: value
     }
}

I have to now pass down:

{
    field1: { set value },
    submodel: {
       update: {
          subfield1: { set: value }
      }
   }
}

Suggested solution

Please support the old syntax, and implicitly take it as “set”.

Alternatives

Additional context

[janpio]

What version are you testing this with @srisub1? 2.6.x got two patch releases 2.6.1 and 2.6.2 as these changes were unwanted and accidental.

Using 2.6.2 or any of the 2.7.x releases you should not observe these differences any more.

[pantharshit00]

Yeah this does seem to be duplicate of https://github.com/graphql-nexus/nexus-plugin-prisma/issues/830. Pleas follow that issue, it has gained quite a lot of upvotes so it is likely to be addressed. Thanks!

I am going to close this here.