Expected Behavior
Java, .Net, Go and Python SDK have consistent method and parameter names.
| Feature |
Type |
Current |
New |
| Service Invocation |
method |
invokeService |
invokeMethod |
| Service Invocation |
parameter |
method |
methodName |
| Service Invocation |
parameter |
request |
data |
| State Store |
method |
saveStates |
saveBulkState |
| State Store |
method |
getStates |
getBulkState |
| State Store |
method |
executeTransaction |
executeStateTransaction |
| State Store |
parameter |
stateStoreName |
storeName |
| Secret Store |
parameter |
secretStoreName |
storeName |
| Binding |
parameter |
name |
bindingName |
| PubSub |
parameter |
topic |
topicName |
| Actor |
method |
invokeActorMethod |
invoke |
| Actor |
method |
registerActorTimer |
registerTimer |
Actual Behavior
Java, .Net, Go and Python SDK have inconsistent method and parameter names.
Steps to Reproduce the Problem
Use any of the methods in different SDKs to notice the difference in naming.
Release Note
RELEASE NOTE: RENAME methods and properties for consistency across SDKs.
Parent: dapr/dapr#2535
Expected Behavior
Java, .Net, Go and Python SDK have consistent method and parameter names.
Actual Behavior
Java, .Net, Go and Python SDK have inconsistent method and parameter names.
Steps to Reproduce the Problem
Use any of the methods in different SDKs to notice the difference in naming.
Release Note
RELEASE NOTE: RENAME methods and properties for consistency across SDKs.
Parent: dapr/dapr#2535