QueryBuilder with a ParseObject encode to json not correct.

[zakiso]

When I use queryBuilder build a query and query condition contains a ParseObject then the server response a error. The error is Unexpected token _ in JSON at position.

This is my code:

///build a query
var queryBuilder = QueryBuilder<ParseObject>(ParseObject("Note"));
var book = ParseObject("Book");
....
///other query limit
....
queryBuilder.whereEqualTo(
            "book",book);

My console out put:

....
....
where={"updatedAt":{ "$gt":{"__type":"Date","iso":"2019-03-23T16:00:00.000Z"}, "$lt":{"__type":"Date","iso":"2019-03-24T15:59:59.000Z"}},"book": {__type: Pointer, className: Books, objectId: HZ09pN5NXI}}&skip=0

[phillwiggins]

I don't quite understand the question, but I can see an error in your query to begin with. Where you call:- queryBuilder.whereEqualTo( "book", ParseObject); Try this instead :- queryBuilder.whereEqualTo( "book", ParseObject("Note"));n Sun, Mar 24, 2019, 09:32 炸鸡叔 <[email protected]> wrote: I use queryBuilder build a query with ParseObject but get error Unexpected

…

token _ in JSON at position from parse server . I checked my request url the parseObject without quotes. This is my code: ///build a query var queryBuilder = QueryBuilder<ParseObject>(ParseObject("Note")); .... ///other query limit .... queryBuilder.whereEqualTo( "book", ParseObject); My console out put: .... .... where={"updatedAt":{ "$gt":{"__type":"Date","iso":"2019-03-23T16:00:00.000Z"}, "$lt":{"__type":"Date","iso":"2019-03-24T15:59:59.000Z"}},"book": {__type: Pointer, className: Books, objectId: HZ09pN5NXI}}&skip=0 The book object without quote. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#138>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgn3rPbe3cO_spU-hp7AQPjQG-vGACRks5vZ0ZJgaJpZM4cFZvP> .

[zakiso]

Sorry for my poor english.
When my query condition contains a parseObject object, the server cannot parse the data correctly.
The Book object should be wrapped in quotes.

[phillwiggins]

Oh right, so none of the elements in the books JSON object are wrapped in quotation marks?

[zakiso]

Yes

[phillwiggins]

Very strange.

What's happens if you create an instance of a Note object and call .toPointer in the whereEqualTo call?

[zakiso]

Oh strange.
Everything works fine when I manually call toPointer.This my console output:

where={"updatedAt":{ "$gt":{"__type":"Date","iso":"2019-03-23T16:00:00.000Z"}, "$lt":{"__type":"Date","iso":"2019-03-24T15:59:59.000Z"}},"book": {"__type":"Pointer","className":"Books","objectId":"HZ09pN5NXI"}}&skip=0

my code:

...
queryBuilder.whereEqualTo(
            "book",book.toPointer());
...

[phillwiggins]

I'll look into that. It probably should be the same output but it looks to be slightly different.

…

On Sun, Mar 24, 2019, 10:10 炸鸡叔 ***@***.***> wrote: Oh strange. Everything works fine when I manually call toPointer.This my console output: where={"updatedAt":{ "$gt":{"__type":"Date","iso":"2019-03-23T16:00:00.000Z"}, "$lt":{"__type":"Date","iso":"2019-03-24T15:59:59.000Z"}},"book": {"__type":"Pointer","className":"Books","objectId":"HZ09pN5NXI"}}&skip=0 my code: ... queryBuilder.whereEqualTo( "book",book.toPointer()); ... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#138 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgn3vjMtqVHLSKohWPbc-J2jschY8w8ks5vZ08RgaJpZM4cFZvP> .

[zakiso]

But when I manually call toPointer, the parse server will not response an error.

[RodrigoSMarques]

@zakiso
Which version are you using? Show your pubscpec.yaml.

The problem with pointers has been resolved.

The correct it use:

queryBuilder.whereEqualTo("field", Object.toPointer());

[zakiso]

@RodrigoSMarques
Everything works fine when I use this method that your provided.
queryBuilder.whereEqualTo("field", Object.toPointer());

[RodrigoSMarques]

@phillwiggins
Close this issue to keep open only what is in trouble.
Resolved according to the above comment