Closed hossam-nasr closed 1 year ago
Closing this issue. Besides CallHttpOptions
, the only other types/interfaces that could be affected by this change would be:
uri
property on the DurableHttpResponse
classstatusQueryGetUri
, sendEventPostUri
, terminatePostUri
, rewindPostUri
and purgeHistoryDeleteUri
properties on the HttpManagementPayload
classcreateNewInstancePostUri
and waitOnNewInstancePostUri
properties on the HttpCreationPayload
class.All of these properties are named this way due to dependencies on the Durable extension. DurableHttpResponse
describes the interface on the CallHttpAction
that the extension expects, while HttpManagementPayload
and HttpCreationPayload
describe the interfaces of properties on the client data input binding value coming from the durable extension.
In all of these cases, we could still rename these properties to url
, while adding logic to change the property names back to uri
when sending to the extension and from uri
coming from the extension, but such logic would be error-prone, and not worth it imo.
FYI @davidmrdavid @ejizba
As in title