Tarantool development patches archive
 help / color / mirror / Atom feed
From: Timur Safin <tsafin@tarantool.org>
To: v.shpilevoy@tarantool.org, alexander.turenko@tarantool.org
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH 2/2] module api: polish module_api test
Date: Thu, 22 Oct 2020 13:20:41 +0300	[thread overview]
Message-ID: <c966bb5aa062113a96b4fe5ad6f93c94c8576c01.1603360022.git.tsafin@tarantool.org> (raw)
In-Reply-To: <cover.1603360022.git.tsafin@tarantool.org>

Use proper doxygen blocks in module_api test

Follow-up to #5348
---
 test/app-tap/module_api.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/test/app-tap/module_api.c b/test/app-tap/module_api.c
index ce7fa2353..0feae0b9b 100644
--- a/test/app-tap/module_api.c
+++ b/test/app-tap/module_api.c
@@ -2287,9 +2287,9 @@ test_tuple_new(struct lua_State *L)
 
 /* }}} test_tuple_new */
 
-/*
+/**
  * Check that argument is a tuple of any format, without
- * its verification
+ * its verification.
  */
 static int
 test_tuple_validate_default(lua_State *L)
@@ -2306,8 +2306,8 @@ test_tuple_validate_default(lua_State *L)
 	return 1;
 }
 
-/*
- * Validate tuple with format of single boolean field
+/**
+ * Validate tuple with format of single boolean field.
  */
 static int
 test_tuple_validate_formatted(lua_State *L)
-- 
2.20.1

  parent reply	other threads:[~2020-10-22 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 10:20 [Tarantool-patches] [PATCH 0/2] module_api: followup changes for merger part Timur Safin
2020-10-22 10:20 ` [Tarantool-patches] [PATCH 1/2] module api: proper documentation for the ibuf wrapper Timur Safin
2020-10-22 10:20 ` Timur Safin [this message]
2020-11-09  5:01   ` [Tarantool-patches] [PATCH 2/2] module api: polish module_api test Alexander Turenko
2020-11-02 21:13 ` [Tarantool-patches] [PATCH 0/2] module_api: followup changes for merger part Vladislav Shpilevoy
2020-11-09  5:03 ` Alexander Turenko

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=c966bb5aa062113a96b4fe5ad6f93c94c8576c01.1603360022.git.tsafin@tarantool.org \
    --to=tsafin@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 2/2] module api: polish module_api test' \
    /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