Compilation errors regarding ServiceClientOptions/OperationSpec with serializer
See original GitHub issueI’m following the instructions mentioned in the README regarding ms-rest-js
/ ms-rest-azure-js
. As you can see in the previous image, the version also matches the one in the README
.
"ms-rest-azure-js": "~0.5.68",
"ms-rest-js": "~0.9.248"
msRest.ServiceClientOptions
and msRest.OperationSpec
seems to miss a serializer
property.
I’m also trying to figure out what is the appropriate upgrade path whenever a version of the extension is bumped.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to fix Script Compilation errors in The Witcher 3 - Gamepur
The first step to fixing any Script Compilation error is to go to download and install the Unification Patch for The Witcher 3....
Read more >The Witcher 3 Script Compilation Errors Explained - GGRecon
Script compilation errors in The Witcher 3 can cause problems for players jumping back into the game with the new 4.0 update.
Read more >Custom error messages in Django Rest Framework serializer
The idea is to try specify error message on model or field level, because as I can see there are no way to...
Read more >How to fix The Witcher 3 script compilation errors
In this guide, we'll break down how to fix the script compilation error message in The Witcher 3. With that you'll be able...
Read more >How to fix Script Compilation errors in The Witcher 3 - MSN
The first step to fixing any Script Compilation error is to go to download and install the Unification Patch for The Witcher 3....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t personally do it-- I use the “literate configuration” to specify a version of the extension I want and mostly don’t worry about the version of the autorest core I’m using.
You can do that with a README.md structured like this (note that the
> see https://aka.ms/autorest
line tells AutoRest that this is an AutoRest config file). This is just going from memory–I haven’t tried running AutoRest with this example config.Please try with
autorest.typescript@2.0.330
. The README is based on whatever is merged to master (what you’ll find under the preview tag under npm.)