createResourceSpecification seems to ignore resourceClassifiedAs field

[vcuculo]

The following mutation

mutation{
  createResourceSpecification(
    resourceSpecification: {
      name:"Fruit and vegatables",
        resourceClassifiedAs: "https://www.wikidata.org/wiki/Q21925565",
    }){
    resourceSpecification{
      id,
      name,
      resourceClassifiedAs
    }
  }
}

results in

{
  "data": {
    "createResourceSpecification": {
      "resourceSpecification": {
        "id": "01FFJCRM7ASFXN8QNA3QKX920D",
        "name": "Fruit and vegatables",
        "resourceClassifiedAs": null
      }
    }
  }
}

should the URL be formatted differently or is ignored in the creation process? Thanks!

[denizenging]

Hi @vcuculo,

Thanks for reporting.

The mutation you use here is incorrect: you should use a list of URIs, not just the URI itself. Nonetheless, it doesn't work with that either, but I made a fix for that; it will be available here soon.

In any case, this has been fixed in ReflowOS.

Cheers, srfsh

[denizenging]

... but I made a fix for that; it will be available here soon.

Sorry for my miscalculation; the change needs some more work. I'll let you know as soon as possible when it is available.

[vcuculo]

Thank you for the update @srfsh . Personally speaking, we moved to the Bonfire backend and therefore this not represent a priority anymore.