Tarantool development patches archive
 help / color / mirror / Atom feed
From: Leonid Vasiliev <lvasiliev@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] error: add format string usage to form a CustomError message
Date: Mon, 1 Jun 2020 15:54:43 +0300	[thread overview]
Message-ID: <63a5bca5-45a6-0f3f-d361-60db93c42941@tarantool.org> (raw)
In-Reply-To: <8cfa7e20-d067-f77d-4300-0b228ad6e440@tarantool.org>

Hi! Thank you for the review.
I updated the commit message:

error: add format string usage to compose a CustomError message

For the CustomError the ability to create a message
using a format string was added.

Closes #4903

@TarantoolBot document
Title: Add format string usage to compose a CustomError message
When an error created using the separate members mode
(box.error(code, errtext[, errtext ...])) in the case of
ClientError error creation, a pre-defined format is used
(corresponding to the error code) (nothing has changed), in
the case of CustomError error creation, a format string can
be used to compose a message.

ClientError(nothing has changed):
```Lua
box.error(code, reason args)
```

Example for ER_CREATE_SPACE:
```Lua
box.error(9, "my_space", "reason")
```
Result:
```Lua
error: 'Failed to create space ''my_space'': reason'
```

CustomError:
```Lua
box.error(type, reason format string, reason args)
```
Example:
```Lua
box.error("MyCustomType", "The error reason: %s", "some error reason")
```
Result:
```Lua
error: 'The error reason: some error reason'
```

On 30.05.2020 01:05, Vladislav Shpilevoy wrote:
> Hi! Thanks for the patch!
> 
> On 28/05/2020 10:31, Leonid Vasiliev wrote:
>> For the CustomError the ability to create a message
>> using a format string was added.
>>
>> Closes #4903
>>
>> @TarantoolBot document
>> Title: Add format string usage to form a CustomError message
>> When creating a ClientError error the predefined format
>> (corresponding with the error code) is used.
>> When creating a CustomError error a format string can be
>> used to form the message.
>>
>> ClientError:
>> ```Lua
>> box.error(code, reason args)
>> ```
>>
>> CustomError:
>> ```Lua
>> box.error(type, reason format string, reason args)
>> ```
> 
> It would be good to provide an example here. And to state, that
> client error case is not changed. Otherwise from the text above
> it looks like you changed it to be 'the predefined format is used'.
> But I will leave it to the doc team to ping you after this is
> pushed.
> 
> Talking of the client error formatting correctness, it looks like
> currently the documentation says:
> https://www.tarantool.io/en/doc/2.3/reference/reference_lua/box_error/#lua-function.box.error
> 
> 	When called with a Lua-table argument, the code and reason have any user-desired values. The result will be those values.
> 
> 	Parameters:
> 
> 	reason (string) – description of an error, defined by user
> 	code (integer) – numeric code for this error, defined by user
> 
> So in the site it is said, that 'reason' is defined by user, not be
> a predefined internal format. The predefined format is used in
> box.error(code, ...) syntax.
> 
>> ---
>> https://github.com/tarantool/tarantool/issues/4903
>> https://github.com/tarantool/tarantool/tree/lvasiliev/gh-4903-format-string-for-CustomError
>> @ChangeLog Add format string usage to form a CustomError message

  reply	other threads:[~2020-06-01 12:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28  8:31 Leonid Vasiliev
2020-05-29 22:05 ` Vladislav Shpilevoy
2020-06-01 12:54   ` Leonid Vasiliev [this message]
2020-06-01 13:47     ` Vladislav Shpilevoy
2020-06-02 14:22 ` Kirill Yukhin

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=63a5bca5-45a6-0f3f-d361-60db93c42941@tarantool.org \
    --to=lvasiliev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] error: add format string usage to form a CustomError message' \
    /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