fix(geoSearch): correct type of MarkerOptions #6319
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This isn't really exposed to the user, but I believe this broke when they moved from a namespace to an interface. fixes #6253
1 task
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 3f366e2:
|
Haroenv
requested review from
a team,
sarahdayan and
shaejaz
and removed request for
a team
aymeric-giraudet
approved these changes
Aug 12, 2024
shaejaz
approved these changes
Aug 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
change MarkerOption from
typeofto a direct access.This isn't really exposed to the user, but I believe this broke when they moved from a namespace to an interface.
Result
No type error in examples provided in the original issue
Still using Marker, not AdvancedMarker (despite Marker being deprecated), changing this would likely be a breaking change.
fixes #6253