How to use multiple cache keys with new RequestResult

[WillooWisp]

I wonder what would be the recommended way of using trackRequestResult to track and cache an entity for multiple cache keys.

• An entity that can be fetched from an API both on id and serial number, I would like to cache on both keys whenever the entity has been fetched with either, so that if trying to fetch with serial and it has already been fetched with id the request won't occur.

Similar to...

trackRequestResult(id ? ["machines", id]) : ["machines", "serial", serialNumber])

• Fetching todos, and you also want to cache each todo on their id, similar to what could be done before.

updateRequestCache("todos"),
updateRequestsCache(
	todos.map(todo => todo.id.toString())
)

[WillooWisp]

@NetanelBasal Sorry to disturb you, but can you point me in the right direction regarding these two caching scenarios?

[NetanelBasal]

trackRequestResult(id ? ["machines", id]) : ["machines", "serial", serialNumber])

LGTM. Any issue?

[WillooWisp]

No that works fine, wondering more about the second use case where you want to fetch a collection and add multiple cache keys, e.g. one for each id for example together with one for the complete collection.

[NetanelBasal]

We'll need to add a setRequestResult function that allows adding new requests from the outside. You're welcome to create a PR.

[WillooWisp]

Okay, I see, that is unfortunate. Hopefully someone with more knowledge in the Elf framework can create such a function then. Until then, can you point me in the right direction for writing such a function? Any good sample code to look at doing something similar?

[NetanelBasal]

We don't have one. You can look at the source code. It shouldn't be hard to expose such a function.

[WillooWisp]

Do you expect the method to look similar to this @NetanelBasal ?

export function setRequestResult(
  keys: unknown[][],
  newValue: Partial<RequestResult>
) {
  for (const key of keys) {
    updateRequestResult(key, newValue);
  }
}

and be used like this?

tap((todos) => store.update(setEntities(todos))),
 trackRequestResult(['todos']),
 setRequestResult(todos.map(todo => ['todos', todo.id]), requestResult),
 setRequestResult(todos.map(todo => ['todos', 'someOtherKey', todo.key]), requestResult)

If so how do I get hold of the request result instance to be passed in to setRequestResult, or how do you expect the usage of it to look like? Or was your suggestion to make setRequestResult the replacement for trackRequestResult but instead allowing it to take in keys as an array of arrays, e.g. keys: unknown[][]?

[NetanelBasal]

Maybe we can do something like:

trackRequestResult(result => {
   return result.todos.map(todo => {
     return { key: ['todos', todo.id], result: todo }
  })
}),

[WillooWisp]

I created a PR to have something to go on with in our discussions...

[WillooWisp]

@NetanelBasal any idea of when we can expect the merged PR to get released?