ensure 'maxResults' limits the number of suggestions too #124
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.
i would expect setting
maxResults
to impact how many suggestions are returned, not geocoding matches.right now, even though 'L.esri.geosearch' passes along a
maxResults
parameter when ultimately calling thefind
operation of the World Geocoding Service, since amagicKey
is included too, only one candidate is ever going to come back.this code change has the desired effect of exposing a technique to augment the number of suggestions returned, but needs a little more testing to make sure all is well with the other providers.