Skip to content
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

Fix telemetry context function type #474

Merged
merged 2 commits into from
Jun 9, 2017
Merged

Conversation

KamilSzostak
Copy link
Contributor

Fixes #434.

@KamilSzostak KamilSzostak added this to the 1.0.10 milestone Jun 8, 2017
@msftclas
Copy link

msftclas commented Jun 8, 2017

@KamilSzostak,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@@ -414,7 +414,7 @@ Sends telemetry to the endpoint.

### addTelemetryInitializer

public addTelemetryInitializer(telemetryInitializer: (envelope: Telemetry.Common.Envelope) => boolean)
public addTelemetryInitializer(telemetryInitializer: (envelope: Telemetry.Common.Envelope) => boolean | void)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it a back compat change (e.g. we now require a Boolean but previously were OK with void)? If not - we may simply want to update instructions in the docs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's a back compatibility change. We were always accepting bool|void, but definition types only allowed boolean.

@KamilSzostak KamilSzostak merged commit 8f8bbd4 into master Jun 9, 2017
@KamilSzostak KamilSzostak deleted the TelemetryContextType branch July 12, 2017 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants