From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kostja@tarantool.org>
Date: Tue, 13 Aug 2019 01:35:04 +0300
From: Konstantin Osipov <kostja@tarantool.org>
Subject: Re: [tarantool-patches] [PATCH 1/1] json: detect a new invalid json
 path case
Message-ID: <20190812223504.GF32337@atlas>
References: <64ddbb6708c2638a04e01a9826773728460345d8.1565480461.git.v.shpilevoy@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <64ddbb6708c2638a04e01a9826773728460345d8.1565480461.git.v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: vdavydov.dev@gmail.com, kshcherbatov@tarantool.org
List-ID: <tarantool-patches.dev.tarantool.org>

* 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


-- 
Konstantin Osipov, Moscow, Russia