Query which accepts multiple arguments doesn't throw with wrong syntax

Taking it from example in docs, the correct syntax to run eq on multiple arguments is eq( predicate, [val1, val2, val3] ) but this would also work eq( predicate, val1, val2, val3 ). Shouldn’t this ideally throw?

Query with correct syntax

{
  steve as var(func: allofterms(name@en, "Steven")) {
    films as count(director.film)
  }

  stevens(func: uid(steve)) @filter(eq(val(films), [1,2,3])) {
    name@en
    numFilms : val(films)
  }
}

Query with incorrect syntax (which also works)

{
  steve as var(func: allofterms(name@en, "Steven")) {
    films as count(director.film)
  }

  stevens(func: uid(steve)) @filter(eq(val(films), 1,2,3 )) {
    name@en
    numFilms : val(films)
  }
}

I think historically we have allowed both formats for both values and uids. It would be a breaking change if we disallowed one of them. Is there a reason why you’d like to disallow one now?

No reason to disallow, came across this when I was testing implementation of uid_in(predicate, [uid1, uid2, uid3], it worked for uid_in(predicate, uid1, uid2, uid3) as well.