docs(hertz): args peekall api (#830)

Author: a631807682

content/en/docs/hertz/tutorials/basic-feature/client.md

@@ -68,7 +68,6 @@ func main() {
 | WithDialFunc                      | network.Dialer | set dialer function. |
 | WithHostClientConfigHook          | nil            | Set the hook function for re-configure the host client. |
 
-
 Sample Code:
 
 ```go
@@ -540,7 +539,7 @@ func main() {
 
 ## Streaming Read Response Content
 
-Hertz's client supports streaming read HTTP response content. 
+Hertz's client supports streaming read HTTP response content.
 
 Since the client has the problem of multiplexing connections, if streaming is used, the connection will be handled by the user(`resp.BodyStream()` is encapsulated by connection) once streaming is used. There are some differences in the management of connections in the above case:
 

content/en/docs/hertz/tutorials/basic-feature/context/request.md

@@ -223,6 +223,7 @@ The Args object provides the following methods to obtain/set `Query String` para
 |`func (a *Args) ParseBytes(b []byte)` |Parsing byte arrays and storing key value pairs in Args object |
 |`func (a *Args) Peek(key string) []byte` |Obtain the value of Args object key |
 |`func (a *Args) PeekExists(key string) (string, bool)` |Obtain the value of Args object key and its existence |
+|`func (a *Args) PeekAll(key string) [][]byte` | Obtain all values of Args object key |
 |`func (a *Args) Len() int`|Obtain the number of Args object key-value pairs |
 |`func (a *Args) AppendBytes(dst []byte) []byte` |Append Args object Query String to dst and return |
 |`func (a *Args) VisitAll(f func(key, value []byte))` |Visit all key value pairs of Args object |
@@ -252,6 +253,8 @@ h.GET("/user", func(c context.Context, ctx *app.RequestContext) {
         // 4. key == []byte("pets"), value == []byte("cat")
     })
 
+    pets := args.PeekAll("pets") // pets == [][]byte{[]byte("dog"), []byte("cat")}
+
     // send information to io.Writer
     req := protocol.AcquireRequest()
 	n, err := args.WriteTo(req.BodyWriter())

content/en/docs/hertz/tutorials/basic-feature/engine.md

@@ -288,7 +288,7 @@ Hertz Server supports streaming write responses.
 Two methods are provided:
 
 1. The user passes in a `io.Reader` through the `ctx.SetBodyStream` function in the handler, and then reads and writes data in blocks in a similar manner to the example code (using channel to control data partitioning and read/write order) **Note that data needs to be written asynchronously**.
-   
+
     If the user knows the total length of the transmitted data in advance, they can pass in the length in the `ctx.SetBodyStream` function for streaming writing, as shown in the example code `/streamWrite1`.
 
     If the user does not know the total length of the transmitted data in advance, they can pass in -1 in the `ctx.SetBodyStream` function to write the stream in the form of `Transfer-Encoding: chunked`, as shown in the example code `/streamWrite2`.

content/en/docs/hertz/tutorials/basic-feature/unit-test.md

@@ -114,7 +114,7 @@ func TestPerformRequest(t *testing.T) {
 
 When executing the [PerformRequest](#performarequest) function, functions such as `NewRecorder`, `Header`, `Write`, `WriteHeader`, `Flush` have already been called internally. The user only needs to call the `Result` function to obtain the returned `protocol.Response` object, and then perform unit testing.
 
-### ResponseRecorder 
+### ResponseRecorder
 
 Used to record the response information of the handler, as follows:
 

content/en/docs/hertz/tutorials/framework-exten/log/zerolog.md

@@ -354,9 +354,10 @@ func main() {
     filePath := filepath.Base(segments[0]) //filepath=="logger.go"
 }
 ```
+
 ### WithCallerSkipFrameCount
 
-`WithCallerSkipFrameCount` adds `caller` to `logger`'s Context. `CallerWithSkipFrameCount` is a method of zerolog's Context structure. It is used to add the caller's file name and line number in the log record, and uses `zerolog.CallerFieldName ` as key name
+`WithCallerSkipFrameCount` adds `caller` to `logger`'s Context. `CallerWithSkipFrameCount` is a method of zerolog's Context structure. It is used to add the caller's file name and line number in the log record, and uses `zerolog.CallerFieldName` as key name
 
 This method accepts a `skipFrameCount` parameter, which specifies the number of stack frames to skip to determine the correct caller location. If the `skipFrameCount` parameter is set to -1, the global `CallerSkipFrameCount` value is used
 

content/en/docs/hertz/tutorials/framework-exten/response_writer.md

@@ -76,6 +76,6 @@ Effect display:
 
 Open the interface in the example at localhost:8888, and then use the following command to observe the effect:
 
-```bash 
+```bash
 curl -N --location localhost:8888/flush/chunk
 ```

content/en/docs/hertz/tutorials/toolkit/command.md

@@ -169,7 +169,7 @@ OPTIONS:
 
 <!---->
 
-- rm_tag value: Remove the specified tag 
+- rm_tag value: Remove the specified tag
 
 <!---->
 
@@ -308,7 +308,7 @@ OPTIONS:
 
 <!---->
 
-- rm_tag value: Remove the specified tag 
+- rm_tag value: Remove the specified tag
 
 <!---->
 
@@ -410,7 +410,7 @@ OPTIONS:
 
 <!---->
 
-- rm_tag value: Remove the specified tag 
+- rm_tag value: Remove the specified tag
 
 <!---->
 
@@ -521,7 +521,7 @@ OPTIONS:
 
 <!---->
 
-- rm_tag value: Remove the specified tag 
+- rm_tag value: Remove the specified tag
 
 <!---->
 

content/en/docs/hertz/tutorials/toolkit/usage-protobuf.md

@@ -12,10 +12,10 @@ description: "hz usage(protobuf)."
 
 1. Create the protobuf IDL file in the current directory
 
-   1. Create api.proto 
+   1. Create api.proto
 
       api.proto is an annotation file provided by hz, with the following content. Please import the file in the annotated proto file.
-      
+
       If you want to expand the use of annotations on your own, please do not use "5" as the beginning of the sequence number to avoid conflicts. For example, "optional string xxx = 77777;".
 
       ```protobuf
@@ -123,7 +123,7 @@ description: "hz usage(protobuf)."
          }
       }
       ```
-   
+
 2. Create a new project
 
    {{< tabs "Execute outside GOPATH" "Execute under GOPATH">}}
@@ -255,7 +255,9 @@ description: "hz usage(protobuf)."
    ```bash
    hz update -I idl -idl idl/hello/hello.proto
    ```
+
 **Note**.
+
 - If the dependency of the IDL is not in the same path as the main IDL, you need to add the `-I` option, which means the path to search for the IDL, equivalent to the `-I` command of protoc.
 - When writing update command, you need to specify not only the IDL file that defines `service`, but also all the dependency files, because protobuf's dependency files will not be updated automatically.
 

content/en/docs/hertz/tutorials/toolkit/usage-thrift.md

@@ -158,7 +158,8 @@ description: "hz usage(thrift)."
    hz update -idl idl/hello.thrift
    ```
 
-**Note**: 
+**Note**:
+
 1. When writing the update command, you only need to specify the IDL file that defines the `service`. hz will automatically generate all the dependencies for that file.
 
 3. As you can see

content/zh/docs/hertz/reference/config.md

@@ -101,4 +101,4 @@ func main() {
 | WithResponseBodyStream | bool | 设置是否使用流式处理，默认关闭 |
 | WithDialFunc | client.DialFunc | 设置 Dial Function |
 | WithWriteTimeout | time.Duration | 写入数据超时时间，默认值：无限长 |
-| WithHostClientConfigHook | func(hc interface{}) error | 设置 hook 函数来重新配置 host client，传入的 func 需要将参数 hc 断言为需要的结构体，比如 http1.HostClient ，再进行具体处理 |
+| WithHostClientConfigHook | func(hc interface{}) error | 设置 hook 函数来重新配置 host client，传入的 func 需要将参数 hc 断言为需要的结构体，比如 http1.HostClient，再进行具体处理 |