Travis Prescott
Travis Prescott
It seems like the `Arguments` class only has annotations for kwarg and vararg, and does not have any property for getting the type comment. Per PEP484, this should be supported...
We can always revive this from git history if need be, but since this is not even in preview, it causes customer confusion when they see this code here.
This is needed to service teams can conform to the updated event guidelines.
These are the current deviations AzureCommunicationCalling has from the guidelines. **Should be addressed in AzureCommunicationCalling 2.4.0** - [ ] SwiftPM support for AzureCommunicationCalling - [ ] Support M1 processors ($ARCH_STANDARD...
Current you would do this by writing a custom `Filter` and using `beforeRecordResponse` to traverse the response and scrub the necessary data. This is a lot of code for something...
AzureTest should be refactored to use the testproxy server.
We use these tools in the build steps for libraries to ensure code style consistency. Issues arise when different versions are used, and if these tools aren't present, the build...
- [ ] Trouter bitcode enabled. [Trouter] - [ ] Trouter to support $ARCH_STANDARD (arm64) [Trouter]
Per API design guidelines, all SDKs must expose API version on the SDK: https://azure.github.io/azure-sdk/ios_design.html#versioning The Calling SDK currently does not support this.
We include a list of headers to scrub by default, but we need a mechanism for test authors to ignore service-specific headers in their tests without updating AzureTest's default list.