无法使用 JsonApiFramework 获取相关资源

Can't get related resource using JsonApiFramework

使用https://github.com/scott-mcdonald/JsonApiFramework框架

我正在从我的 UI 发送以下 PATCH:

{"data":{"id":"4221fe2f-ca7b-425d-b45a-a09f4936a22b","attributes":{"contact-trade-name":"asdad","contact-name":"aasd","contact-phone":"asdad","contact-email":"asdad@adasd.asd","created-date":"2016-12-19T14:07:59.833","status":"AwaitingBillData"},"relationships":{"share-user":{"data":{"type":"users","id":"5078b2ee-2348-44f5-95a0-3c14c2ad2b1d"}}},"type":"jobs"}}

在我的服务器上,我正在执行以下操作:

using (var documentContext = new DocumentContext(HttpContext.Current.Request.Url, document)) { var job = documentContext.GetResource<Job>(); var relationships = documentContext.GetResourceRelationships(job); var shareUserRel = relationships["share-user"]; var shareUser = documentContext.GetRelatedResource<Data.ServiceModel.User>(shareUserRel); }

然而 shareUser 总是 null

shareUserRel 在我检查时有以下内容:

{ResourceIdentifier [type=users id=5078b2ee-2348-44f5-95a0-3c14c2ad2b1d]}

如果有帮助的话。

有什么明显的地方我可能做错了吗?

要格式化 json:api 文档以提高可读性,它看起来像这样:

{
  "data": {
    "type": "jobs"
    "id": "4221fe2f-ca7b-425d-b45a-a09f4936a22b",
    "attributes": {
      "contact-trade-name": "asdad",
      "contact-name": "aasd",
      "contact-phone": "asdad",
      "contact-email": "asdad@adasd.asd",
      "created-date": "2016-12-19T14:07:59.833",
      "status": "AwaitingBillData"
    },
    "relationships": {
      "share-user": {
        "data": {
          "type": "users",
          "id": "5078b2ee-2348-44f5-95a0-3c14c2ad2b1d"
        }
      }
    }
  }
}

GetRelatedResource returning null 的原因是您要求文档上下文 return 文档中实际包含的不存在的用户资源在文档中。

当客户端在 PATCH 中发送此类 json:api 文档时,您是在指示服务器使用给定属性更新作业资源,并将此作业资源关联到在一对一资源链接。

在您的示例中拥有关系对象后,更正确的内容如下:

if (shareUserRel.IsResourceLinkageNullOrEmpty())
{
  // Clear any linkage between the job resource and any current user
  ...
}
else
{
  var shareUserResourceIdentifier = shareUserRel.GetToOneResourceLinkage();
  // Create linkage between the job resource and existing user identified
  // by shareUserResourceIdentifier
  ...
}

现在如何处理“...”取决于您的数据层。