This repository has been archived by the owner on Dec 21, 2020. It is now read-only.

Better error handling #35

Open

karussell opened this issue Jan 2, 2017 · 2 comments

Member

karussell commented Jan 2, 2017

Instead of just "bad request" the client should print the detailed message

Current workaround something like:

System.out.println(exception.getResponseBody().toString());

Member

boldtrn commented Jan 11, 2017

This is for the swagger generated client, isn't it?

Member Author

karussell commented Jan 11, 2017 •

edited

Loading

Yes, currently just the geocoding ... related/duplicate issue: https://github.com/graphhopper/directions-api-clients-route-optimization/issues/6

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.