From ecdc18790b79abdcbad162289533d7612822e2cd Mon Sep 17 00:00:00 2001
From: Pavel Semyonov <p.semyonov@vk.team>
Date: Mon, 16 Jan 2023 16:04:00 +0700
Subject: [PATCH] Fix line length
NO_CHANGELOG=changelog
NO_DOC=changelog
NO_TEST=changelog
---
changelogs/unreleased/gh-3211-per-module-log_level.md | 4 ++--
.../unreleased/gh-6650-round-with-big-precision.md | 3 ++-
changelogs/unreleased/gh-6832-httpc-params-encoding.md | 3 ++-
.../unreleased/gh-6833-decode-body-http-response.md | 8 ++++----
.../unreleased/gh-6833-encode-body-http-request.md | 10 +++++-----
5 files changed, 15 insertions(+), 13 deletions(-)
diff --git a/changelogs/unreleased/gh-3211-per-module-log_level.md b/changelogs/unreleased/gh-3211-per-module-log_level.md
index 75ccbe317c..2e4c8466f1 100644
--- a/changelogs/unreleased/gh-3211-per-module-log_level.md
+++ b/changelogs/unreleased/gh-3211-per-module-log_level.md
@@ -3,5 +3,5 @@
* **[Breaking change]** Now the log message contains the name of a module from
which the logging function was called (gh-3211).
-* Now the log level can be set for specific modules using `log.cfg{modules = {...}}` or
- `box.cfg{log_modules = {...}}` (gh-3211).
+* Now the log level can be set for specific modules using `log.cfg{modules = {...}}`
+ or `box.cfg{log_modules = {...}}` (gh-3211).
diff --git a/changelogs/unreleased/gh-6650-round-with-big-precision.md b/changelogs/unreleased/gh-6650-round-with-big-precision.md
index 75eb1fb198..b2bbd11f5a 100644
--- a/changelogs/unreleased/gh-6650-round-with-big-precision.md
+++ b/changelogs/unreleased/gh-6650-round-with-big-precision.md
@@ -1,3 +1,4 @@
## bugfix/sql
-* Now the `ROUND()` functions works correctly on arguments with big precision (gh-6650).
+* Now the `ROUND()` functions works correctly on arguments with big precision
+ (gh-6650).
diff --git a/changelogs/unreleased/gh-6832-httpc-params-encoding.md b/changelogs/unreleased/gh-6832-httpc-params-encoding.md
index 6269320dff..ebbfb1e5ae 100644
--- a/changelogs/unreleased/gh-6832-httpc-params-encoding.md
+++ b/changelogs/unreleased/gh-6832-httpc-params-encoding.md
@@ -1,4 +1,5 @@
## feature/lua/http client
* Added a new option `params` to add query parameters to URI using a Lua table.
- These parameters are encoded to a query string and passed to the HTTP request (gh-6832).
+ These parameters are encoded to a query string and passed to the HTTP request
+ (gh-6832).
diff --git a/changelogs/unreleased/gh-6833-decode-body-http-response.md b/changelogs/unreleased/gh-6833-decode-body-http-response.md
index 7f9fbbb4e6..66b4ed8382 100644
--- a/changelogs/unreleased/gh-6833-decode-body-http-response.md
+++ b/changelogs/unreleased/gh-6833-decode-body-http-response.md
@@ -1,7 +1,7 @@
## feature/lua/http client
* Added a new method `response:decode()`. It decodes an HTTP response body to
- a Lua object. The decoding result depends on the response content type. The following
- content types are supported by default: `application/json`, `application/yaml`,
- `application/msgpack`. Users can define decoding rules for other content types
- by writing their own decoding functions. (gh-6833).
+ a Lua object. The decoding result depends on the response content type. The
+ following content types are supported by default: `application/json`,
+ `application/yaml`, `application/msgpack`. Users can define decoding rules for
+ other content types by writing their own decoding functions (gh-6833).
diff --git a/changelogs/unreleased/gh-6833-encode-body-http-request.md b/changelogs/unreleased/gh-6833-encode-body-http-request.md
index 9caf0d785d..632447925c 100644
--- a/changelogs/unreleased/gh-6833-encode-body-http-request.md
+++ b/changelogs/unreleased/gh-6833-encode-body-http-request.md
@@ -1,7 +1,7 @@
## feature/lua/http client
-* Now the HTTP client is able to encode Lua objects automatically when it is possible.
- The encoding format depends on the request content type. The following
- content types are supported by default: `application/json`, `application/yaml`,
- `application/msgpack`. Users can define encoding rules for other content types
- by writing their own encoding functions. (gh-6833).
+* Now the HTTP client is able to encode Lua objects automatically when it is
+ possible. The encoding format depends on the request content type.
+ The following content types are supported by default: `application/json`,
+ `application/yaml`, `application/msgpack`. Users can define encoding rules
+ for other content types by writing their own encoding functions (gh-6833).
--
GitLab