Skip to content

Remove coordinate limit from MapboxMapMatching#940

Merged
danesfeder merged 1 commit into
masterfrom
dan-matching-limit
Dec 17, 2018
Merged

Remove coordinate limit from MapboxMapMatching#940
danesfeder merged 1 commit into
masterfrom
dan-matching-limit

Conversation

@danesfeder

Copy link
Copy Markdown
Contributor

This PR removes the hard-coded check for a max of 100 coordinates in MapboxMapMatching. Developers are able to pay for and configure higher coordinate limits, so we shouldn't enforce this in the java code - the error code / message will still be returned from the server.

cc @kbauhaus @Guardiola31337

@Guardiola31337 Guardiola31337 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for running with this @danesfeder 🚢

@Guardiola31337 Guardiola31337 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if the same thing applies for waypointNames 🤔

throw new ServicesException("Waypoint names exceed 500 character limit.");
I believe so, right? @danesfeder @osana If so, we should remove ☝️ check too.

@osana osana left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe MapMatching has and Error handling.
It would be good to modify/move the test instead of deleting it.

@osana osana mentioned this pull request Dec 18, 2018
14 tasks
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.

3 participants