Return of the "Invalid use of comma"!

[abhijit-kar (Abhijit Kar ツ)]

I am facing the same issue as topic attached below.

queryTweets works, but getTweets does not work

The bug is because even though the field id represents an xid and has type String! because of its name we were considering it to be an ID. So for example the following schema would work type Tweets { twitterID: String! @id score: Int } Only when the name of the field with @id directive is id, this would break. We should have been checking for the type of the field instead of the name. I have fixed this in fix(GraphQL): Fix getType queries when id was used as a name for types other than ID b…

Even though the PR is marked merged, the issue still persists in Slash GraphQL.

And I don’t want to use a workaround like naming my id as something else, as id looks slick and consistent with the rest.

Excerpt from my schema, which causes the issue:

type User {
	"""
	UID Generated by Firebase, to identify a User.
	"""
	id: String! @id
}

I don’t want to use fid, or firebaseID.

P.S. Slash prevented me from using uid, while I was setting the schema, which is better than giving error half way through.

[pawan (Pawan Rawal)]

Fair enough, we should have this deployed to Slash today or early next. You can keep track of the Slash releases at Topics tagged release