This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
@hlship some time ago you talked about taking attributes on demand in the resolvers of lacinia, optimizing the case where :user/name is in one "place" and :user/friends is in another "place". #pathom do that.
:user/name
:user/friends
I've lost the context for this, but I'd guess it could be a cache of data for entities with the scope of the executing GraphQL query.