Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

IdentifiedRef.load broke in 3.0.0-rc.1

See original GitHub issue

When I bump from 3.0.0-rc to 3.0.0-rc.1, this code is no longer working:

    async email(root) {
      const client = await root.load();
      return client.email;
    },

Where root is an IdentifiedReference.

I don’t see a tag for rc vs. rc.1 to do a compare and scan for likely changes, so I don’t really have much more information than “it started happening in 3.0.0-rc.1”

(I had been on 3.0.0-rc.3 and it had the broken behavior as well; it looks like 3.0.0-rc it was working fine and then regressed in 3.0.0-rc.1.

Issue Analytics

State:
Created 4 years ago
Comments:14 (8 by maintainers)

Top GitHub Comments

1reaction

B4nancommented, Dec 14, 2019

Fixed in 3.0.0-rc.4.

1reaction

B4nancommented, Dec 13, 2019

So the problem was that the correction was happening only for the merged entity, but it was not cascaded to its relations.

Tricky part was to actually remove the need for always present EM instance, but I cracked that as well. Will fix the rest of the bugs first before releasing next RC, probably during weekend.