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

[libtelemetry] Add LocationEvent constructor that doesn't accept permissionStatus #569

Conversation

mr1sunshine
Copy link
Contributor

In #566 we added permissionStatus parameter to the LocationEvent constructor. That change actually introduced a breaking change in the public API surface.
With this change, we are bringing an old constructor back and we use the unknown default value for the permissionStatus.

@mr1sunshine mr1sunshine force-pushed the mr1sunshine/bring-back-location-event-without-permission-status branch from 4347081 to afc115f Compare June 7, 2022 07:49
@mr1sunshine mr1sunshine marked this pull request as ready for review June 7, 2022 07:53
…ermissionStatus`

In #566 we added `permissionStatus` parameter to the `LocationEvent`
constructor. That change actually introduced a breaking change in the
public API surface.

With this change, we are bringing an old constructor back and we use
the `unknown` default value for the `permissionStatus`.
@mr1sunshine mr1sunshine force-pushed the mr1sunshine/bring-back-location-event-without-permission-status branch from afc115f to e6ee1a8 Compare June 7, 2022 10:10
@mr1sunshine mr1sunshine requested a review from pengdev June 7, 2022 10:10
@mr1sunshine mr1sunshine merged commit e6ee1a8 into main Jun 7, 2022
@mr1sunshine mr1sunshine deleted the mr1sunshine/bring-back-location-event-without-permission-status branch June 7, 2022 10:37
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