[Bug] Derived loader doesn't behave as expected

Bug report

When using a derived loader I get a confusing error. My basic setup is this:

// SCHEMA
type Pool {
  # `Pool-${token0.toHexString()}-${token1.toHexString()}`
  id: ID!
  stakingPool: StakingPool
}
type StakingPool {
  id: Bytes!
  liquidityPool: Pool!
}

// WHEN ADDING THE POOL FIRST
poolEntity.stakingPool = idOfFutureStakingPool;


const stakingPool = StakingPool.load(poolAddress)!;
const lp = stakingPool.liquidityPool.load()[0];

The last line is crashing with the error:
Mapping aborted at ~lib/@graphprotocol/graph-ts/common/value.ts, line 80, column 5, with message: Value is not a string.

What am I doing wrong? I didn't find any documentation for this modifier or any other for the subgraph. Also if I did anything wrong shouldn't the loader return an empty array instead of exploding in my face?

Using the derived field works well (in inspecting the store) but using the loader doesn't.

Relevant log output

No response

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux

Commencez par reproduire l’exemple de derived-loader de l’issue, puis inspectez lib/@graphprotocol/graph-ts/common/value.ts autour de la ligne 80, où l’erreur signalée se produit. Suivez la manière dont stakingPool.liquidityPool.load() gère le schéma et le mapping présentés ; le travail est terminé lorsqu’il est établi si le problème vient de l’utilisation ou du loader, et que le comportement attendu est documenté ou corrigé.