From 7d257fa980086394700e86fa9e5ae7a982c6e6bf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Roger=20Vi=C3=B1as=20Alcon?= Date: Fri, 10 Nov 2023 20:23:46 +0100 Subject: [PATCH] Improve doc (#14) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 46a7991..16454e3 100644 --- a/README.md +++ b/README.md @@ -152,7 +152,7 @@ interface MyEventConsumer { Then we follow these steps: -### 1) We configure the binding `my-consumer` in application.yml but declaring it as a function: +### 1) We declare the binding `my-consumer` in application.yml: ```yaml spring: cloud: @@ -171,7 +171,7 @@ spring: * We configure a `group` because we want the application to consume from Kafka identifiying itself as a consumer group so if there were to be more than one instance of the application every message will be delivered to only one of the instances. * As stated in [functional binding names](https://docs.spring.io/spring-cloud-stream/docs/current/reference/html/spring-cloud-stream.html#_functional_binding_names): `my-consumer` is the function name, `in` is for input bindings and `0` is the index we have to use if we have a single function. -### 2) We create the same class `MyStreamEventConsumer` but implementing `Consumer` to fulfill the interface required by Spring Cloud Stream: +### 2) We create the same class `MyStreamEventConsumer` implementing `Consumer` to fulfill the interface required by Spring Cloud Stream: ```kotlin class MyStreamEventConsumer(private val consumer: MyEventConsumer) : Consumer { override fun accept(payload: MyEventPayload) {