Querying the same relation multiple times as aliases with different args results in wrong data about join-monster HOT 5 CLOSED

I did some experiments in a fork, and stumbled upon the skipped test it should handle duplicate object type fields with different arguments that should cover this case. I added my own test in kryops@d6e1a26

The best I could come up with for now is a workaround: kryops@f75a574

• If a field has an alias, it is not only written to row[fieldName], but also to row[fieldName + '$' + alias]
• Fields with args have to set resolve: aliasAwareResolver, which prefers the aliased key over the default one
• I did not look at pagination as we use SQLite which currently does not support it

While this is still far from a viable solution, maybe it could be used as a starting point for a proper fix?

from join-monster.

Ah, I finally found #126, so it seems I created a duplicate 😕

from join-monster.

I just recently ran into this issue as well. Its surprising that its a bug that's been around for years because it seems like its such a common use case. I can assist where needed to help get this fix out.

from join-monster.

While my workaround seems to work quite well for 1:n relationships, it seems to fail miserably for aliased 1:1 relationships because @stem/nesthydrationjs does not like hydrating the same source fields into multiple nested targets - instead it just sets everything to null 😞

const { nest } = require('@stem/nesthydrationjs');

console.log(nest(
  { id: '1', foo: 'bar' },
  {
    id: 'id',
    child: { foo: 'foo' },
    child$alias: { foo: 'foo' },
  }
));

// { id: '1', child: null, 'child$alias': null }

from join-monster.

I am closing this in favor of #126

from join-monster.