Jose Manuel Heredia Hidalgo
Jose Manuel Heredia Hidalgo
Something similar happens with Inline array definitions where the values are defined as nameless enums: https://github.com/Azure/autorest.typescript/blob/f7448a0c800f7fd3b84e37e4e4e02fd85f737075/test/integration/swaggers/appconfiguration.json#L1056 We get Enum1, Enum2, Enum3, etc.
I think that's a good idea and we'd be leveraging TS representing these definitions inline. Other languages that can't do this would still have the problem, right? They'll need a...
+1 on both points. We can move the logging policy and keep the default auth where it is now, shouldn't affect the auth path since 4xx errors are not retried...
Hmm looks like we're not getting the expected namespace. I'm looking into this now
/azp run prepare-pipelines
/azp run confidentialledger - tests
/azp run js - confidentialledger - tests
js - confidential-ledger-rest - tests
/azp run js - confidential-ledger-rest - tests
I like the idea of having these `clientlets` one thing I would like to set clear before we start working on this, is how we plan to gather the information...