Bug: id.startsWith is not a function about offix HOT 4 CLOSED

This is happening when the model is missing id field or id field is not a string
@Hasan-git I will quickly patch it as this looks like a blocker for me.

I think we have 2 issues here. The first one is that we always assume id is a string and this is a critical issue that I will patch and release fix today.

The second one will be the fact that we ignore MutationHelperOptions.idFIeld provided by the user and use the hardcoded id field in IDProcessor - Going to create a separate issue for that bug.

Can you provide me a value of the id field that is triggering this issue to make sure that my fix is going to address it?

To fix this bug we need:

• Make additional check for id and transform it to string
• Document the MutationHelperOptions.idFIeld for customization needs

from offix.

Can you provide me a value of the id field that is triggering this issue to make sure that my fix is going to address it?

Indeed, the whole object was null. if its does matter that I was doing a mutation that should return an GraphqlError but I didn't , maybe if I was returning an GraphqlError this bug will not be catched

from offix.

@Hasan-git This makes sense now. Going to patch this and do new patch release.

from offix.

Done. Going to release 0.6.1

from offix.