I have a query for login:
query {
loginUser(username: "Test 1", password: "hello")
}
which gives following in Playground:
{
"data": null,
"errors": [
{
"message": "Can't convert '\"fnED2f3OLXACBwPPrLxk4AYI-ETyHFHNN3eLFBhe2jdnACmipuo\"' to Vector",
"path": [
"loginUser"
],
"locations": [
{
"line": 2,
"column": 3
}
]
}
]
}
I correctly receive a token but with the error message.
I reviewed this posting:
and added
@resolver(name: "login_user", paginated: true)
to the schema and uploaded it.
Now, with:
query {
loginUser(username: "Test 1", password: "hello" )
{
data {
secret
}
}
}
I get:
"data": null,
"errors": [
{
"message": "Field 'data' of type 'String' must not have a sub selection. (line 3, column 5):\n data {\n ^",
"locations": [
{
"line": 3,
"column": 5
}
]
}
]
}
but with:
query {
loginUser(username: "Test 1", password: "hello" )
}
I get:
{
"data": null,
"errors": [
{
"message": "Field 'loginUser' of type 'QueryLoginUserPage!' must have a sub selection. (line 2, column 3):\n loginUser(username: \"Test 1\", password: \"hello\")\n ^",
"locations": [
{
"line": 2,
"column": 3
}
]
}
]
}
This is perhaps because I haven’t implemented:
Map(
Paginate(
Filter(
etc. in the query, as per the posting. However, as a beginner, I don’t have the FQL experience to modify my function to this extent (and perhaps the ‘vector’ error is just a bug anyway: vector bug (?)).
- Is this still a bug and I just need to wait for a fix?
- Is there something I can do in the meantime?
thanks …