Narrow geocode param types #44
Closed
+6
−4
Conversation
This file contains hidden or 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
elchukc
force-pushed
the
narrow-geocode-param-types
branch
from
88eafa9 to
9820df9
Compare
elchukc
force-pushed
the
narrow-geocode-param-types
branch
from
9820df9 to
9c9d36f
Compare
|
Thanks for contributing with these changes. This has been manually merged in now. |
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.
Currently, if you pass all the fields allowed by the type system to
geocoder.geocode(), the API will return warnings that it was not expecting.Without changing any functionality, this change to the declaration file improves developer experience for TypeScript users by having the typing system more closely match the alternate URL parameters laid out in the docs.
Also updates library version to 1.10.0 in
package-lock.json.