Bug:Parse filter incorrectly

[johnny94]

Issue Summary

I was trying to use filter attribute in get helper, and found it can't generate the correct query statement.
(Note: Maybe this issue is related to GQL )

Steps to Reproduce

The following code will generate the expected query statement:

var test_filter = gql.parse('tag:new-tag,tag:hello-ghost,featured:false');
gql.json.printStatements(test_filter.statements);

Result
 { op: '=', value: 'new-tag', prop: 'tag' }
 { op: '=', value: 'hello-ghost', prop: 'tag', func: 'or' }
 { op: '=', value: false, prop: 'featured', func: 'or' }

While this one will generate the wrong query statement:

var test_filter = gql.parse('tag:new-tag,tag:hello-ghost+featured:false'); // replace the last , with +
gql.json.printStatements(test_filter.statements);

Result
{ op: '=', value: 'new-tag', prop: 'tag' }
{ op: '=', value: 'hello-ghost', prop: 'tag', func: 'or' }

Expected
{ op: '=', value: 'new-tag', prop: 'tag' }
{ op: '=', value: 'hello-ghost', prop: 'tag', func: 'or' }
{ op: '=', value: false, prop: 'featured', func: 'and'}

But this work as expected:

var test_filter = gql.parse('featured:false+tag:new-tag,tag:hello-ghost'); // move featured:false to the forefront of the query
gql.json.printStatements(test_filter.statements);

Result
{ op: '=', value: false, prop: 'featured' }
{ op: '=', value: 'new-tag', prop: 'tag', func: 'and' }
{ op: '=', value: 'hello-ghost', prop: 'tag', func: 'or' }

I think this behavior is really strange.

Technical details

• Ghost Version: 0.7.4
• Client OS: Windows 10
• Server OS: Windows 10
• Node Version: 0.10.41
• Browser: Chrome 47.0.2526.106 m
• Database: sqlite 3

[ErisDS]

Hey @johnny94, thanks for the thorough bug report. I'm pretty sure this is a bug in GQL, although a strange one.

[ErisDS]

I'm closing all OAuth and most API issues temporarily with the later label.

RE: OAuth, for the next 2-3 months we'll be implementing an official Ghost OAuth login system, providing global access to all Ghost blogs with a single login. We'll be opening issues around this system soon, and I don't want to cause confusion with OAuth for the API.

JSON API Overhaul & OAuth access are currently scheduled next on the roadmap