-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.0.465 removed addUserAgentInfo from ServiceClient which is a breaking change #276
Comments
Hi sgellock. |
Related to Azure/autorest.typescript#386. |
@sgellock Did my previous comment solve the problem for you? |
I'm going to close this issue. Feel free to reopen if my proposed solution doesn't work. |
This is not a solution because it BREAKS existing clients that depend on this library. you can't do this, it is unprofessional. If you are going to break it you need to do a major version change. |
For future references, in #313 we changed ServiceClientOptions.userAgent to be either a string or a function that takes in the defaultUserAgent string and then returns the string that the ServiceClient will use. This should enable previous scenarios where people simply wanted to append to the existing user-agent string, and it should also enable other scenarios too (prepending, inserting, or whatever else someone wants to do with the defaultUserAgent string). |
We generated code using 1.0.455. This generated code is crashing when our customers install botbuilder, as pulls in the 1.0.465.
Looks like this method was removed with the following commit:
523b891#diff-3b5c4e8e88ea4820a88a9584a654fe8cL144
Expected behavior
Following semver rules, patch versions should not be breaking.
The text was updated successfully, but these errors were encountered: