dapr 0.1.18 → 0.1.20

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 799c05f8d8605bc143ba8a423cbcf141fb3b42f157efec50171fd071064b84e9
-  data.tar.gz: 80d22d6b23ee2a1b035133702210d8fb9575a3cd7f56d4d6f9d80e0e9d61c3c0
+  metadata.gz: 8df47b206023dca8719858a4804d26d2ebafa509bddb478b91bede1cc4218d62
+  data.tar.gz: 950c92173973547e2865de8ea19733a0cd01c2740871e12c2eea3dc7de1c58b2
 SHA512:
-  metadata.gz: 67dfca3d49d95550858b5dbd5c55c2dc890db598d7e1e06da3ce126cba3ec492ba18cce0f46e53b992475a22ef9557ac8eab6b48513bf8ab2bb46f4ae4e85087
-  data.tar.gz: 44402e4fdcbf197aeb5404254419f2caafd57e724ca648d3ad456fd85be71b2c24e25d313fa3e2fb06da8fedc53a97a5a109c01e4f4685c9f48f8d3dd456c0d3
+  metadata.gz: 7b71595b5f08a7c41c16f2dfb1c77dfd2d82e45a3d18a87a1cc2ef69a164d9eb481af8e4e024d4c7de7dc11796d3db4de135c3ba9d06aa07fae9bae7d14a25a4
+  data.tar.gz: abda725498346865e3adc1d8102bb1ceee7dcc08170b5d409a0e5b29fc81b50817cd80f3aac71fc9338abfcd25700f992a32248833127edd3a354bd522c61b3c

data/Readme.adoc

@@ -6,7 +6,17 @@
 :caution-caption: :fire:
 :warning-caption: :warning:
 endif::[]
-:dapr-building-block: https://docs.dapr.io/concepts/building-blocks-overview/[Dapr Building Block]
+:dapr-building-block: https://docs.dapr.io/concepts/building-blocks-concept/[Dapr Building Block]
+:pubsub-block: https://docs.dapr.io/developing-applications/building-blocks/pubsub/pubsub-overview/[Dapr Pub/Sub Building Block]
+:state-block: https://docs.dapr.io/developing-applications/building-blocks/state-management/state-management-overview/[Dapr State Management Building Block]
+:actors-block: https://docs.dapr.io/developing-applications/building-blocks/actors/actors-overview/[Dapr Actor Building Block]
+:binding-block: https://docs.dapr.io/developing-applications/building-blocks/bindings/bindings-overview/[Dapr Binding Building Block]
+:secret-block: https://docs.dapr.io/developing-applications/building-blocks/secrets/secrets-overview/[Dapr Secret Building Block]
+:configuration-block: https://docs.dapr.io/developing-applications/building-blocks/configuration/configuration-api-overview/[Dapr Configuration Building Block]
+:distributed-lock-block: https://docs.dapr.io/developing-applications/building-blocks/distributed-lock/distributed-lock-api-overview/[Dapr Distributed Lock Building Block]
+:workflow-block: https://docs.dapr.io/developing-applications/building-blocks/workflow/workflow-overview/[Dapr Workflow Building Block]
+:cryptography-block: https://docs.dapr.io/developing-applications/building-blocks/cryptography/cryptography-overview/[Dapr Cryptography Building Block]
+
 
 == Overview
 
@@ -34,7 +44,11 @@ is a more opinionated and higher-level abstraction.
 Each {dapr-building-block} is exposed as a class under the `Rubyists::Dapr::Client` or
 `Rubyists::Dapr::Service` namespace.
 
-=== Publish a message
+=== Pub/Sub
+
+Implementation of {pubsub-block}
+
+==== Publish a message
 
 [source,ruby]
 ----
@@ -47,27 +61,65 @@ publisher.publish('topic-name', { message: 'Hello, Dapr!', from: 'Ruby' })
 <2> Create a new publisher for the `pubsub-name` pubsub component. This component must be defined in the Dapr runtime.
 <3> Publish a message to the `topic-name` topic.
 
-=== Subscribe to topics
+==== Subscribe to topics
 
 Subscriptions in Dapr work a little different than you may be used to. Instead of subscribing to a topic
 then looping through consumed messages, you define a fully-fledged service that Dapr will
-send each message to in the topic(s) that you specify. This unique appreach allows you to
+send each message to in the topic(s) that you specify. This unique approach allows you to
 focus on the business logic of your service, rather than the plumbing of message consumption.
 
 [source,ruby]
 ----
 require 'dapr/service/subscriber'
 handler = ->(event) { puts "Got event: #{event}" } <1>
-pubsub_name: 'pubsub' <2>
-sub = Rubyists::Dapr::Service::Subscriber.new(pubsub_name:, topics: 'TOPIC-A', handler: handler) <3>
-sub.start! <4>
+pubsub_name = 'pubsub' <2>
+topics = 'TOPIC-A' <3>
+sub = Rubyists::Dapr::Service::Subscriber.new(pubsub_name:, topics:, handler:) <4>
+sub.start! <5>
 ----
 <1> Define a handler that will be called for each message received. `event` will be a `CloudEvents::Event` instance.
++
+NOTE: The handler can be anything that responds to `#call`, such as a lambda, proc, or instance. Sky's the limit! (Dependency injection, anyone?)
++
 <2> The name of the Dapr pubsub component this subscriber will utilize.
-<3> Create a new subscriber for the `pubsub` pubsub component, subscribing to the `TOPIC-A` topic.
-<4> Start the subscriber. This will block the current thread and call the handler for each message received.
+<3> The name of the topic(s) to subscribe to.
++
+TIP: Multiple topics can be subscribed to simultaneously by passing an array of topic names to the `topics` argument.
++
+<4> Create a new subscriber for the `pubsub` pubsub component, subscribing to the `TOPIC-A` topic.
+<5> Start the subscriber. This will block the current thread and call the handler for each message received.
+
+=== State Management
+
+Implementation of {state-block}
+
+=== Actors
+
+Implementation of {actors-block}
+
+=== Bindings
+
+Implementation of {binding-block}
+
+=== Secrets
+
+Implementation of {secret-block}
+
+=== Configuration
+
+Implementation of {configuration-block}
+
+=== Distributed Lock
+
+Implementation of {distributed-lock-block}
+
+=== Workflow
+
+Implementation of {workflow-block}
+
+=== Cryptography
 
-TIP:: Multiple topics can be subscribed to simultaneously by passing an array of topic names to the `topics` argument.
+Implementation of {cryptography-block}
 
 == Development
 

data/lib/dapr/version.rb

@@ -2,6 +2,6 @@
 
 module Rubyists
   module Dapr
-    VERSION = '0.1.18'
+    VERSION = '0.1.20'
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dapr
 version: !ruby/object:Gem::Version
-  version: 0.1.18
+  version: 0.1.20
 platform: ruby
 authors:
 - Tj (bougyman) Vanderpoel