POST /works: 500 when provided field not in context

[lautarodragan]

POST /works
{
  "name": "string",
  "datePublished": "2019-01-31T09:21:54.567Z",
  "dateCreated": "2019-01-31T09:21:54.567Z",
  "author": "string",
  "tags": "string",
  "text": "string"
}

The text field should be content, but it shouldn't return a 500.

{
  "level": 50,
  "time": 0,
  "msg": "api.CreateWork",
  "pid": 25,
  "hostname": "",
  "module": "works",
  "exception": {
    "stack": [
      "Error: The property \"text\" in the input was not defined in the context.",
      "    at options.expansionMap.info (/usr/src/app/api/node_modules/jsonld-signatures/lib/suites/LinkedDataSignature.js:97:17)",
      "    at _expandObject (/usr/src/app/api/node_modules/jsonld/lib/expand.js:356:26)",
      "    at Object.api.expand (/usr/src/app/api/node_modules/jsonld/lib/expand.js:176:3)",
      "    at _expandObject (/usr/src/app/api/node_modules/jsonld/lib/expand.js:620:29)",
      "    at api.expand (/usr/src/app/api/node_modules/jsonld/lib/expand.js:176:3)",
      "    at /usr/src/app/api/node_modules/jsonld/lib/jsonld.js:327:18",
      "    at process._tickCallback (internal/process/next_tick.js:68:7)"
    ],
    "message": "The property \"text\" in the input was not defined in the context.",
    "type": "Error"
  },
  "v": 1
}

[WesleyCharlesBlake]

The API docs in swagger hub have the correct schema, but I know it used to be text. Possibly wrong implementation by someone sending the text field here. Regardless we could handle this better. Thanks for logging the issue!

[lautarodragan]

Yeah. The underlying issue is incorrect handling of input not matching default schema, which is related to #552.

People are sending text rather than content because the frost-client typings are out of date, victim of copy pasta, tracked in poetapp/frost-client#220.