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
We have reported similar modular issue but this issue still exists in RLC.
Say we have Foo and Bar responses and we would generate below overloadings. But if the definition of these two operations are the same or Bar is subset of Foo's, our overloading would be not working. This is because TypeScript is duck-typing it compares the definition with shape not interface names.
This usually happened in LRO operations where the initial response is the same but the final response is different. So we can't correctly predict the logical response.
exportfunctiongetLongRunningPoller(response: FooResponse|FooDefaultResponse,): response is FooDefaultResponse|FooLogicalResponse;exportfunctiongetLongRunningPoller(response: BarResponse|BarDefaultResponse,): response is BarDefaultResponse|BarLogicalResponse;
The same issue would happen in isUnexpected helper.
The text was updated successfully, but these errors were encountered:
MaryGao
changed the title
getLongRunningPoller not working if one model is a subset of another model in RLC
getLongRunningPoller not working if response definitions are the same between operations
Nov 15, 2024
We have reported similar modular issue but this issue still exists in RLC.
Say we have Foo and Bar responses and we would generate below overloadings. But if the definition of these two operations are the same or Bar is subset of Foo's, our overloading would be not working. This is because TypeScript is duck-typing it compares the definition with shape not interface names.
This usually happened in LRO operations where the initial response is the same but the final response is different. So we can't correctly predict the logical response.
The same issue would happen in isUnexpected helper.
The text was updated successfully, but these errors were encountered: