Values from @example should be used as exact values

Reported by @sepehr500 in #25

Currently, if want to fake a string, I do the following

type CourtCase {
  jurisdiction: String @examples(values: ["DFT", "FUR"])
}

This makes the think that values expects it’s value to be an array of whatever the property type is. So it would follow, that if the type was the following,

type CourtCase {
  jurisdiction: [String] @examples(values: [["DFT", "FUR"],["DFS","DNA"])
}

Since the property type is now an array of strings, it would make sense to pass in an array of strings into the array to match the return type. So if we take this same logic an apply it to Objects, then we would expect a property that has a type that is an array of objects, to look like the following,

type Query {
  allCourtCases: [CourtCase!]!
     @examples(values: [[{state: "WASH", capital: "SEA"},{state: "VA", capital: "RMD"}], [{state:"VA"}]])
}

This way, you have a consistent rule that values always expects an array of whatever type the return type of the property is.

[nmoore93]

Hi, I was just wondering if this was something you still plan to add as part of the version 2.0.0 release? It would be great to specify an exact array to return, for example:

type Query {
  letters: [String] @examples(values: [["A", "B", "C"]])
}

Then running the query:

{
  letters
}

always returns the array [“A”, “B”, “C”] in that order. Thanks!

[IvanGoncharov]

@sepehr500 Thank you for suggestions 👍 Right now working on a new GraphQL project, so will put this issue on hold. But after releasing it I will try to iterate on this and other issues and release version 2.0.0.