handle no-route errors about disease-info HOT 5 CLOSED

We can create a new strategy to handle the API errors, not only 404, but 422 or 401 or other HTTP errors.
as this is a JSON API we don't need to return html responses but just json response, something like this:

{  
   errors:{  
      resource:[  
         "Some explanation about the error"
      ]
   },
   data:{ 
   }
}

I can think how to handle this.

from disease-info.

Surely it will not be for only 404. I was thinking with @sunday to redirect to the HTML public document provided. But with this comment I agree we should do away with HTML. I will deal with it using rescue_from and simplify it to handle other errors as well.

from disease-info.

@luizvarela @SundayAdefila @osioke I have added root route in this commit.

from disease-info.

@SundayAdefila @luizvarela Solved. This is what I came up with here also Route/diseases to root in this commit. However @luizvarela I beg of you to write test for this PR after merged.

from disease-info.

Fixed with #58

from disease-info.