FuzzyMatch query param missing from forwardGeocode
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 768
- Forks
- 191
- PR merge metrics
- No merged PRs in 30d
Description
i was trying to use the FuzzyMatch param from the API docs today, & i got the error the fuzzyMatch keys isn't valid, so i went & check the geocoding.js file & yeah fuzzyMatch isn't here
```
Geocoding.forwardGeocode = function(config) {
v.assertShape({
query: v.required(v.string),
mode: v.oneOf('mapbox.places', 'mapbox.places-permanent'),
countries: v.arrayOf(v.string),
proximity: v.coordinates,
types: v.arrayOf(v.oneOf(featureTypes)),
autocomplete: v.boolean,
bbox: v.arrayOf(v.number),
limit: v.number,
language: v.arrayOf(v.string)
})(config);
config.mode = config.mode || 'mapbox.places';
var query = stringifyBooleans(
xtend(
{ country: config.countries },
pick(config, [
'proximity',
'types',
'autocomplete',
'bbox',
'limit',
'language'
])
)
);
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in geocoding.js at Geocoding.forwardGeocode, reviewing both the config validation and the query parameter selection shown in the issue. Confirm that fuzzyMatch is accepted and forwarded to the API, then verify the resulting request behavior with the repository's relevant geocoding checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100