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

[Annotation plugin] Add GeoJsonOptions to allow to configure the underlying used GeoJsonSource #79

Merged
merged 2 commits into from
Feb 22, 2021

Conversation

Chaoba
Copy link
Contributor

@Chaoba Chaoba commented Feb 5, 2021

PRs must be submitted under the terms of our Contributor License Agreement CLA.
Fixes: < Link to related issues that will be fixed by this pull request, if they exist >

Pull request checklist:

  • Briefly describe the changes in this PR.
  • Include before/after visuals or gifs if this PR includes visual changes.
  • Write tests for all new functionality. If tests were not written, please explain why.
  • Add example if relevant.
  • Document any changes to public APIs.
  • Apply changelog label ('breaking change', 'bug 🪲', 'build', 'docs', 'feature 🍏', 'performance ⚡', 'testing 💯') or use the label 'skip changelog'
  • Add an entry inside this element for inclusion in the mapbox-maps-android changelog: <changelog>[Annotation plugin] Add GeoJsonOptions to allow to configure the underlying used GeoJsonSource</changelog>.

Summary of changes

This pr add a config class GeoJsonOptions to allow to configure the underlying used GeoJsonSource and add toString method for Layer

User impact (optional)

@Chaoba Chaoba self-assigned this Feb 5, 2021
@Chaoba Chaoba requested a review from a team February 5, 2021 06:56
@Chaoba Chaoba force-pushed the kl-annotation-options branch from 34944d7 to f064436 Compare February 5, 2021 09:23
@Chaoba Chaoba requested a review from tobrun February 19, 2021 09:03
@Chaoba Chaoba merged commit faee8a8 into main Feb 22, 2021
@Chaoba Chaoba deleted the kl-annotation-options branch February 22, 2021 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants