Router is filling in a null object with all the null fields inside the object

[golfingal72]

[See my datatypes below] When i return a null on the RetailerOrganization below from a subgraph response, the final response is returning:
"retailerOrganization":{"allowedFeatures":null,"retailers":null}

the APOLLO-SERVER in NODE JS is returning in the final federated response...
"retailerOrganization":null

Which is the PREFERRED answer i'd like to see..

I've tried it 2 ways: not returning the reference to the retailerOrganization in the SUBGRAPH Response AND returning a specific null in the body: "retailerOrganization": Null

demonstrated object types:

type RetailerOrganization {
  allowedFeatures: [ConnectFeatureContractFeature]
  retailers: [Retailer]
}

type FullUser @key(fields: "id options") @extends {
   id: Long @external
  email: String @external @obfuscateRequestLogging
  options: UserRenderParms @external
  retailerOrganization: RetailerOrganization @requires(fields: "id email")
}

[abernix]

Is your question in #1375 the same concern or very closely related to this? (It seems to be?)

[Geal]

@cris-santos just to clarify, what is your user subgraph returning for { currentUser { activeOrganization { id } } ?

[cris-santos]

@Geal this is the response when I run the query on the user subgraph:

it's the same response I get when running the same query on the router

but if I try to get cretorUser for example, it also returns the error

[Geal]

Ok there's probably a bug here, I'll look into it

[cris-santos]

@Geal, thank you. If you need more info, just let me know!

[Geal]

@cris-santos thanks, I got enough to reproduce it in #1819. I think I know where it comes from, I should have a fix next week