Add warning message to `dapr-client` builds
See original GitHub issueProposal
Per #207, add deprecation warnings to the dapr-client
package builds and direct the user to move to @dapr/dapr
.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Placement Service not called for Actor Using Dotnet SDK and ...
I'm instantiating from a minimal API project and I don't see any entries past the application protocol: http. waiting on port 3000. log...
Read more >DaprClient usage - Dapr Docs
Essential tips and advice for using DaprClient. ... Create your own classes for top-level messages, events, or state values so you can add...
Read more >The Dapr publish & subscribe building block - Microsoft Learn
With any other status-code than 200 or 404 , a warning is logged and the message is retried. Alternatively, Service B can explicitly...
Read more >Dapr for .NET Developers - GitHub
interested in learning how to build applications designed for the cloud. ... A warning is logged and the message is dropped.
Read more >Dapr PubSub with dotnet SDK - Stack Overflow
Add the [FromBody] attribute to the action method parameter. For example: public async Task<ActionResult> SubscribeAsync([FromBody] Message ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can’t… I don’t have access to the
dapr-client
packageHello @XavierGeerinck, the versioning feature request is now being tracked separately. The PR for warning users on using dapr-client package is up and will close this issue.