React-Apollo Mutation返回空响应

Question

我正在使用AWS Appsync,我希望从成功执行的变异中获得响应.当我在Appsync Graphql控制台中尝试我的设置时,我得到一个填充的"data": { "mutateMeeting" }响应:

当我在我的反应应用程序中尝试相同时,我可以在dynamodb数据库中看到突变发生,但react-apollo不会返回突变响应.正如您在apollo开发工具中看到的那样,"data": { "mutateMeeting" }为null:

我错过了什么？

相应的graphql架构读取:

input MeetingInput {
  id: String,
  start: String!,
  end: String!,
  agreements: [AgreementInput]!
}

type Meeting {
  id: String!
  start: String!
  end: String!
  agreements: [Agreement]
}

type Mutation { 
  mutateMeeting (
    companyId: String!,
    meeting: MeetingInput!
  ): Meeting!
}

在graphql标签突变写着:

import gql from 'graphql-tag'

export default gql`
  mutation mutateMeeting($companyId: String!, $meeting: MeetingInput!) {
    mutateMeeting(companyId: $companyId, meeting: $meeting) {
      id,
      start,
      end
    }
  }
`

和反应-阿波罗 inklusion由下式给出:

import React, { Component } from 'react'
// antd
import { Spin } from 'antd'
// graphql
import { compose, graphql } from 'react-apollo'
import mutateMeeting from '../queries/mutateMeeting'

class MeetingStatus extends Component {
  componentDidMount() {
    const { mutateMeeting, meeting } = this.props
    console.log(meeting)
    const variables = {
      companyId: meeting.company.id,
      meeting: {
        start: meeting.start.toISOString(),
        end: meeting.end.toISOString(),
        agreements: meeting.agreements,
      }
    }
    console.log(variables)

    mutateMeeting({
      variables
    }).then(({data}) => console.log('got data', data))
    .catch(err => console.log(err))
  }

  render() {
    console.log(this.props)
    return <div>convocado</div>
  }
}

const MeetingStatusWithInfo = compose(
  graphql(mutateMeeting, { name: 'mutateMeeting' })
)(MeetingStatus)

export default (MeetingStatusWithInfo)

Appsync请求

#set($uuid = $util.autoId())
#set($batchData = [])
#set( $meeting = ${context.arguments.meeting} )

## Company
#set( $meetingMap = {
  "PK" : $context.arguments.companyId,
  "SK" : "Meeting-$uuid",
  "start" : $meeting.start,
  "end" : $meeting.end
} )
$util.qr($batchData.add($util.dynamodb.toMapValues($meetingMap)))

## Meeting
$util.qr($meetingMap.put("PK", $meetingMap.SK))
$util.qr($batchData.add($util.dynamodb.toMapValues($meetingMap)))

## Agreements
#foreach($agreement in $meeting.agreements)
  #set( $agreementId = $util.autoId())
  #set( $agreementMap = {
    "PK" : $meetingMap.SK,
    "SK" : "Agreement-$agreementId",
    "name" : $agreement.name
  } )

  $util.qr($batchData.add($util.dynamodb.toMapValues($agreementMap)))
#end

{
  "version" : "2018-05-29",
  "operation" : "BatchPutItem",
  "tables": {
    "Vysae": $utils.toJson($batchData)
  }
}

Appsync响应:

#set( $meeting = $context.result.data.Vysae[1] )
{
  "id": "$meeting.PK",
  "start": "$meeting.start",
  "end": "$meeting.end"
}

Answer 1

看起来这个错误有一个未解决的问题。本期原版中还有更多详细信息。

SessionQuery 中的用户信息最初将被 UserProfile 组件缓存和监视。当UpdateAvatarMutation执行并返回时，UserProfile组件中的查询将收到空数据。其他几个人也观察到了这种行为，并将其追溯到查询/缓存字段与突变返回的字段之间的不完美重叠（在此示例中，突变返回结果的用户节点中缺少电子邮件）。

换句话说，如果您的查询返回相同类型的对象，并且查询和突变之间的字段不匹配，则最终可能会得到空数据。这不是预期的行为，但如果这是这种情况下的根本问题，您可以尝试确保查询和突变的请求字段相同。