I18n support for all Grape exceptions

[niedhui]

eg:
raise Grape::Exceptions::ValidationError, :status => 400, :param => attr_name, :message => "invalid parameter: #{attr_name}"

can invalid parameter be I18n compatible

[dblock]

There's nothing built-in into Grape for this, but since this is something that happens at runtime, can you just do the translation as you do it for the rest of your strings?

[niedhui]

Hi, I found grape denpends on activesupport, and activesupport depends on I18n, will this be a feature

[dblock]

If you contribute it, I would definitely take it.

[niedhui]

thanks, I'll try it later

[dblock]

There're several places where Grape calls raise with message text. We want all exceptions to start inheriting a base class and add i18n support everywhere. Mongoid does a fantastic job at this, which I've reused in the heroku-forward gem: https://github.com/dblock/heroku-forward/tree/master/lib/heroku/forward/errors - I want something like that.

[niedhui]

I had took a vacation these days, and return to work now, I'll do it this week. : )

[niedhui]

Hi, I'm doing the all-exception-i18n work.
Move all translation to Grape::Exceptions::Base, Implment problem/summary/resolution exception message.
and found sometimes ,it's a little verbose to show problem/summary/resolution long exception message,
especially for the validation errors. the validation error message will show for the end user, not api developer, so simple 'the age must be integer' is better for 'problem:xxxx\n summary:yyy\n'.
So Here's what I had done.

grape:
  errors:
     messages:
       missing_vendor_option1:  missing :vendor option.
       missing_vendor_option2:
          problem: 'missing :vendor option.'
          summary: 'when version using header, you must specify :verdor option. '
          resolution: "eg: version 'v1', :using => :header, :vendor => 'twitter'"

the error message for missing_vendor_option1 is just the simple 'missing :vendor option.'
and the error message for missing_vendor_option2 is the verbose one
I had push my code:
niedhui@f6e3d95

Just want to make sure I'm on the right way /

thanks

[dblock]

Yep, that's on the right track.

[dblock]

Closing, thanks @niedhui for the implementation.