From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <v.shpilevoy@tarantool.org>
Subject: Re: [tarantool-patches] Re: [PATCH 1/1] json: detect a new invalid
 json path case
References: <64ddbb6708c2638a04e01a9826773728460345d8.1565480461.git.v.shpilevoy@tarantool.org>
 <20190812223504.GF32337@atlas>
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Message-ID: <fac38058-94aa-bb25-b02d-15ed11ae4da0@tarantool.org>
Date: Tue, 13 Aug 2019 21:47:23 +0200
MIME-Version: 1.0
In-Reply-To: <20190812223504.GF32337@atlas>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
To: tarantool-patches@freelists.org, Konstantin Osipov <kostja@tarantool.org>
Cc: vdavydov.dev@gmail.com, kshcherbatov@tarantool.org
List-ID: <tarantool-patches.dev.tarantool.org>

Pushed to 1.10 - master branches.

On 13/08/2019 00:35, Konstantin Osipov wrote:
> * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/08/11 10:01]:
>> JSON paths has no a strict standard, but definitely there is no
>> an implementation, allowing to omit '.' after [], if a next token
>> is a key. For example:
>>
>>     [1]key
>>
>> is invalid. It should be written like that:
>>
>>     [1].key
>>
> 
>> Strangely, but we even had tests on the invalid case.
>>
>> Closes #4419
> 
> This has to go to 1.10.
> 
> lgtm
> 
>