From c4cd7bdb2c1b2852f297dc571ae87102c19eb9f1 Mon Sep 17 00:00:00 2001
From: zhangchao <zchao9100@gmail.com>
Date: Tue, 25 Jul 2023 22:59:10 +0800
Subject: [PATCH] add example

Signed-off-by: zhangchao <zchao9100@gmail.com>
---
 .../supported-middleware/middleware-wasm.md   | 45 ++++++++++++++++++-
 1 file changed, 44 insertions(+), 1 deletion(-)

diff --git a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md
index c93bf3953..f81b2a6f5 100644
--- a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md
+++ b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md
@@ -47,7 +47,7 @@ How to compile this is described later.
 | Field | Details                                                        | Required | Example        |
 |-------|----------------------------------------------------------------|----------|----------------|
 | url   | The URL of the resource including the Wasm binary to instantiate. The supported schemes include `file://`. The path of a `file://` URL is relative to the Dapr process unless it begins with `/`. | true     | `file://hello.wasm` |
-| guestConfig   | The configuration for the wasm function, its format depends on how the wasm function parses it. | false     | `enviroment=production`,`{"environment":"production"}` |
+| guestConfig   | An optional configuration passed to WASM guests. Users can pass an arbitrary string to be parsed by the guest code. | false     | `enviroment=production`,`{"environment":"production"}` |
 
 ## Dapr configuration
 
@@ -119,6 +119,49 @@ If using TinyGo, compile as shown below and set the spec metadata field named
 tinygo build -o router.wasm -scheduler=none --no-debug -target=wasi router.go`
 ```
 
+### wasm config example
+
+Here is an example of how to use `guestConfig` to pass configurations to wasm. In wasm code, you can use the function `handler.Host.GetConfig` defined in guest sdk to get the configuration. In the following example, the wasm middleware parses the executed `environment` from json config defined in the component.
+
+```yaml
+apiVersion: dapr.io/v1alpha1
+kind: Component
+metadata:
+  name: wasm
+spec:
+  type: middleware.http.wasm
+  version: v1
+  metadata:
+  - name: url
+    value: "file://router.wasm"
+  - guestConfig
+    value: {"environment":"production"}
+```
+Here's an example in TinyGo:
+
+```go
+package main
+
+import (
+	"encoding/json"
+	"github.com/http-wasm/http-wasm-guest-tinygo/handler"
+	"github.com/http-wasm/http-wasm-guest-tinygo/handler/api"
+)
+
+type Config struct {
+	Environment string `json:"environment"`
+}
+
+func main() {
+	// get config bytes, which is the value of guestConfig defined in the component.
+	configBytes := handler.Host.GetConfig()
+	
+	config := Config{}
+	json.Unmarshal(configBytes, &config)
+	handler.Host.Log(api.LogLevelInfo, "Config environment: "+config.Environment)
+}
+```
+
 
 ## Related links