Skip to content

Conversation

@danesfeder
Copy link
Contributor

Underlying code working with LocationEngine in the LocationLayerPlugin was updated, but the methods annotating the required permissions for certain methods were not. These changes rearrange the annotations to reflect the new code changes.

@danesfeder danesfeder added the location-layer-plugin Issues that deal with the location layer module label May 18, 2018
@danesfeder danesfeder self-assigned this May 18, 2018
mapView.removeOnMapChangedListener(onMapChangedListener);
}

void onLocationLayerStart() {
Copy link

@cammace cammace May 19, 2018

Choose a reason for hiding this comment

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

Any reason for changing the access modifiers here? Changing to private causes a synthetic accessor method to be created. In my opinion, it should be the opposite, we should prevent synthetic accessor methods from being created everywhere possible as this adds to the method count.

@zugaldia

@danesfeder
Copy link
Contributor Author

@cammace will the permission annotations in this PR conflict with the engine work being re-added in #527?

@danesfeder danesfeder force-pushed the dan-remove-permission branch from 76fb496 to 3ff71a0 Compare May 22, 2018 18:18
@cammace
Copy link

cammace commented May 22, 2018

Not sure why it would since the engine is internal, none of the public APIs are changed.

@danesfeder danesfeder merged commit fe9b7ee into master May 22, 2018
@danesfeder danesfeder deleted the dan-remove-permission branch May 22, 2018 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

location-layer-plugin Issues that deal with the location layer module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants