Apollo Server Federation 沒有解決？

Question

首先感謝您閱讀本文，我花了最后一天的時間來解決這個我根本無法弄清楚的錯誤。 我之前有它工作過，但由於某種原因它停止了。 基本上，所有服務都按預期獨立工作。 但是，一旦我嘗試引用另一個（假設我正在使用配置文件服務並想從帳戶服務中提取 email），它只會返回 null。 沒有錯誤信息，什么都沒有。 我添加了重要的代碼片段，但如果您想查看整個代碼庫，請告訴我，我會將其推送到 github。

帳戶類型定義：

import { gql } from 'apollo-server';

const typeDefs = gql`
  # SCALARS
  """
  An ISO 8601-encoded UTC date string...
  """
  scalar DateTime
  # OBJECTS
  """
  An account is an Auth0 user that provides authentication details.
  """
  type Account @key(fields: "id") {
    "The unique Auth0 ID associated with the account."
    id: ID!
    "The date and time the account was created."
    createdAt: DateTime!
    "The email associated with the account (must be unique)."
    email: String
    "Whether the account is blocked."
    isBlocked: Boolean
    "Whether the account has a moderator role."
    isModerator: Boolean
  }

帳戶解析器：

 Account: {
    __resolveReference(reference, { dataSources }, info) {
      return dataSources.accountsAPI.getAccountById(reference.id);
    },
    id(account, args, context, info) {
      return account.user_id;
    },
    createdAt(account, args, context, info) {
      return account.created_at;
    },
    isModerator(account, args, context, info) {
      return (
        account.app_metadata &&
        account.app_metadata.roles &&
        account.app_metadata.roles.includes('moderator')
      );
    },
    isBlocked(account, args, context, info) {
      return account.blocked;
    },
  },

配置文件類型定義：

      extend type Account @key(fields: "id") {
        id: ID! @external
        "Metadata about the user that owns the account."
        profile: Profile
      }
  type Profile @key(fields: "id") {
    "The unique MongoDB document ID of the user's profile."
    id: ID!
    "The Auth0 account tied to this profile."
    account: Account!
    "The URL of the user's avatar."
    avatar: String
    "A short bio or description about the user (max. 256 characters)."
    description: String
    "Other users that the user follows."
    following(
      first: Int
      after: String
      last: Int
      before: String
      orderBy: ProfileOrderByInput
    ): ProfileConnection
    "The full name of the user."
    fullName: String
    "The URL of the user's GitHub page."
    githubUrl: String
    "The user's pinned GitHub repositories and gists."
    pinnedItems: [PinnableItem]
    "The unique username of the user."
    username: String!
    "Whether the currently logged in user follows this profile."
    viewerIsFollowing: Boolean
  }

輪廓解析器：

Profile: {
    account(profile, args, context, info) {
      return { __typename: 'Account', id: profile.account_id };
    },
}

Answer 1

在寫這篇文章時，我意識到問題出在哪里，所以我會把它貼在這里，這樣你們就不必浪費時間了。 我還不明白為什么，我會盡快跟進，但由於某種原因，我擁有的權限（使用 grahpql-shield）。 打破一切，在創建聯合服務時將其注釋掉后，它神奇地開始工作，對於那些好奇的人，這是我的權限。

賬戶許可

import { and, or, rule, shield } from 'graphql-shield';

import getPermissions from '../../lib/getPermissions';

const canReadAnyAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('read:any_account');
});

const canReadOwnAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('read:own_account');
});
const canEditOwnAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('edit:own_account');
});
const canBlockAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('block:any_account');
});
const canPromoteAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('promote:any_account');
});
const isReadingOwnAccount = rule()(
  (parent, { id }, { user }, info) => user.sub === id,
);

const isEditingOwnAccount = rule()(
  (parent, { where: { id } }, { user }, info) => user.sub === id,
);

const permissions = shield(
  {
    Query: {
      account: or(
        and(canReadAnyAccount, isEditingOwnAccount),
        canReadAnyAccount,
      ),
      accounts: canReadAnyAccount,
    },
    Mutation: {
      changeAccountBlockedStatus: canBlockAccount,
      changeAccountModeratorRole: canPromoteAccount,
      deleteAccount: and(canEditOwnAccount, isEditingOwnAccount),
      updateAccount: and(canEditOwnAccount, isEditingOwnAccount),
    },
  },
  { debug: process.env.NODE_ENV === 'development' },
);

export default permissions;

配置文件權限：

import { and, or, rule, shield } from 'graphql-shield';

import getPermissions from '../../lib/getPermissions';

const canReadAnyAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('read:any_account');
});

const canReadOwnAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('read:own_account');
});
const canEditOwnAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('edit:own_account');
});
const canBlockAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('block:any_account');
});
const canPromoteAccount = rule()((parent, args, { user }, info) => {
  const userPermissions = getPermissions(user);

  return userPermissions && userPermissions.includes('promote:any_account');
});
const isReadingOwnAccount = rule()(
  (parent, { id }, { user }, info) => user.sub === id,
);

const isEditingOwnAccount = rule()(
  (parent, { where: { id } }, { user }, info) => user.sub === id,
);

const permissions = shield(
  {
    Query: {
      account: or(
        and(canReadAnyAccount, isEditingOwnAccount),
        canReadAnyAccount,
      ),
      accounts: canReadAnyAccount,
    },
    Mutation: {
      changeAccountBlockedStatus: canBlockAccount,
      changeAccountModeratorRole: canPromoteAccount,
      deleteAccount: and(canEditOwnAccount, isEditingOwnAccount),
      updateAccount: and(canEditOwnAccount, isEditingOwnAccount),
    },
  },
  { debug: process.env.NODE_ENV === 'development' },
);

export default permissions;

我還要感謝來自 8 bit-press 的 Mandi，因為她是我用她那本很棒的書學習 graphql 的原因。 這里或那里可能存在一些錯誤（尚不確定，因為我很容易犯錯誤，如果不是這可能是一個錯誤，並且對其他閱讀本書的人有用），但我當然建議任何想要學習 apollo 的人檢查一下https://8bit.press/book/advanced-graphql