Rpc Client UserProperties
Open
feature-request
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
### Description
Why is there no way to pass in UserProperties, ContentType... and such into the `IMqttRpcClient`'s `ExecuteAsync`?
This is rather annyoing, as it doesn't register userProperties from the given `IMqttClient` either.
### Suggestion
an overload to `ExecuteAsync` that simply takes in a `MqttApplicationMessage`
### Related to
- MQTTnet.Extensions.Rpc
Contributor guide
No contributing guide indexed for this repository
Research direction
In MQTTnet.Extensions.Rpc, trace IMqttRpcClient.ExecuteAsync and how the RPC message is currently supplied. Compare the requested MqttApplicationMessage path with the existing API, and verify that UserProperties and ContentType can be passed through when the change is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100