dapr 0.1.18 → 0.1.19

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 799c05f8d8605bc143ba8a423cbcf141fb3b42f157efec50171fd071064b84e9
-  data.tar.gz: 80d22d6b23ee2a1b035133702210d8fb9575a3cd7f56d4d6f9d80e0e9d61c3c0
+  metadata.gz: 67d8484ce4365b192ba1756fa63085371e3224370b500a341a3ca2428581a0d3
+  data.tar.gz: c97c4d0b0e40940039f83dc041a81897b958086ba38d1a96b560d6e86dc25874
 SHA512:
-  metadata.gz: 67dfca3d49d95550858b5dbd5c55c2dc890db598d7e1e06da3ce126cba3ec492ba18cce0f46e53b992475a22ef9557ac8eab6b48513bf8ab2bb46f4ae4e85087
-  data.tar.gz: 44402e4fdcbf197aeb5404254419f2caafd57e724ca648d3ad456fd85be71b2c24e25d313fa3e2fb06da8fedc53a97a5a109c01e4f4685c9f48f8d3dd456c0d3
+  metadata.gz: b19abf8c5983476ee14abfe9235fc84f34055a6ab49148bc9eef369a56ee20ca56e5f36e491e1de0e08c3c5cf85b3cb1bc4aad8696f442aaa21eb041f3e5f461
+  data.tar.gz: 565d9d2296feda65259fc5c0b30c5f462a6c44399ae97b7b3d1581751e541c9dc46fa9a1023bfe0924358b3ef870a5c857b17dd9b1263e03531606f8a286c47a

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,7 +61,7 @@ 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
@@ -58,16 +72,54 @@ focus on the business logic of your service, rather than the plumbing of message
 ----
 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.19'
   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.19
 platform: ruby
 authors:
 - Tj (bougyman) Vanderpoel