You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Declarative subscription guide illustrates subscribing to a orders topic with route to the subscription as /checkout. This is already confusing since the example uses checkout entity as being the 'publisher'. Why is the publisher subscribing..?
Programmatic subscription guide with Python illustrates subscribing to a checkout topic with route to the subscription as /order. This is breaking consistency with the first example which the doc states is being replicated in the prog-subscription documentation. For folks like me, who don't know better, this will cause a lot of confusion.
In the declarative subscription, why does scopes include both checkout and orderprocessing ..? isn't it supposed to be just orderprocessing that is subscribing..?
rakeshwalisheter
changed the title
Documentation is misleading for folk trying this out for the first time
Documentation/Tutorials for setting up PubSub component are unclear
Aug 19, 2024
Describe the issue
orders
topic with route to the subscription as/checkout
. This is already confusing since the example usescheckout
entity as being the 'publisher'. Why is the publisher subscribing..?checkout
topic with route to the subscription as/order
. This is breaking consistency with the first example which the doc states is being replicated in the prog-subscription documentation. For folks like me, who don't know better, this will cause a lot of confusion.scopes
include bothcheckout
andorderprocessing
..? isn't it supposed to be justorderprocessing
that is subscribing..?URL of the docs
https://docs.dapr.io/developing-applications/building-blocks/pubsub/subscription-methods/#declarative-subscriptions
https://docs.dapr.io/developing-applications/building-blocks/pubsub/subscription-methods/#programmatic-subscriptions
Expected content
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: