Dgraph isn't automatically setting values ​​as list in structured mutations as list.

[MichelDiz]

If you suspect this could be a bug, follow the template.

• What version of Dgraph are you using?
  1.1RC

• Have you tried reproducing the issue with latest release?
  Yes, latest RC

• Steps to reproduce the issue (command/config used to run Dgraph).
  Add a list mutation in JSON before set the schema.

• Expected behaviour and actual result.
  Since Dgraph automatically recognizes Types (Like [uid] this is a "list") I think it should recognize a list through a structured mutation as a list. Avoiding the user lost some data from his list. In case he forgets to define the scheme before mutating.

I didn't tested it in RDF tho. Will do.

Check reference: #3787

[martinmr]

Not really a bug so I've changed the tag. The reason uid is set to list is to preserve the existing behavior (since uid used to be a list by default).

[campoy]

Ok, I got the issue here.

If we send a mutation like this one without setting any schema:

{
  "set": [
    {
      "name": "beethoven",
      "likes": [
        "food",
        "music"
      ]
    }
  ]
}

a query like this one:

{
  q(func: eq(name, "beethoven")) {
    name
    likes
  }
}

Will only contain one of the likes.

{
  "data": {
    "q": [
      {
        "name": "beethoven",
        "likes": "music"
      }
    ]
  },
  "extensions": { }
}

I would say this is a bug too.