From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: vdavydov.dev@gmail.com, kshcherbatov@tarantool.org
Subject: Re: [tarantool-patches] [PATCH 1/1] json: detect a new invalid json path case
Date: Tue, 13 Aug 2019 01:35:04 +0300 [thread overview]
Message-ID: <20190812223504.GF32337@atlas> (raw)
In-Reply-To: <64ddbb6708c2638a04e01a9826773728460345d8.1565480461.git.v.shpilevoy@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
next prev parent reply other threads:[~2019-08-12 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 23:43 Vladislav Shpilevoy
2019-08-12 22:35 ` Konstantin Osipov [this message]
2019-08-13 19:47 ` [tarantool-patches] " Vladislav Shpilevoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190812223504.GF32337@atlas \
--to=kostja@tarantool.org \
--cc=kshcherbatov@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=vdavydov.dev@gmail.com \
--subject='Re: [tarantool-patches] [PATCH 1/1] json: detect a new invalid json path case' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox