Call Initialize in third constructor

[mawt]

A call to Initialize is missing in the third constructor

/// <summary>
/// Initializes a new instance of the CatFactory class.
/// </summary>
/// <param name='baseUri'>
/// Optional. The base URI of the service.
/// </param>
/// <param name='credentials'>
/// Required. Subscription credentials which uniquely identify client subscription.
/// </param>
/// <param name='handlers'>
/// Optional. The delegating handlers to add to the http client pipeline.
/// </param>
public CatFactory(Uri baseUri, ServiceClientCredentials credentials, params DelegatingHandler[] handlers) : this(handlers)
{
    if (baseUri == null)
    {
        throw new ArgumentNullException("baseUri");
    }
    if (credentials == null)
    {
        throw new ArgumentNullException("credentials");
    }
    this.BaseUri = baseUri;
    this.Credentials = credentials;
    // Missing call to this.Initialize()?
}

Nb. this ought to be tested, as I'm just passing by.

[azuresdkci]

Can one of the admins verify this patch?

[azurecla]

Hi @mawt, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

[devigned]

Thank you for the contribution. We'll review it shortly.

[hovsepm]

@azuresdkci test this please

[hovsepm]

@mawt,
This change is not required since Initialize is called inside this(handlers) constructor.

public CatFactory(Uri baseUri, ServiceClientCredentials credentials, params DelegatingHandler[] handlers) 
: this(handlers)
{
...

[mawt]

Apologies - I missed that :( Constructor chaining is something I advise against.