Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error formatter new argument change not documented #1905

Open
Timunas opened this issue Sep 10, 2019 · 2 comments
Open

Error formatter new argument change not documented #1905

Timunas opened this issue Sep 10, 2019 · 2 comments
Labels

Comments

@Timunas
Copy link

@Timunas Timunas commented Sep 10, 2019

Custom error formatter must have now 5 arguments instead of the old 4. These changes were introduced here on #1652

When migrating from 0.19 to 1.1.0 I had issues on a custom error formatter because the original_exception argument was introduced but that change was not documented on the upgrading guide.

@dblock dblock added the bug? label Sep 11, 2019
@dblock
Copy link
Member

@dblock dblock commented Sep 11, 2019

Appreciate a PR to fix the docs, thanks.

@myxoh
Copy link
Member

@myxoh myxoh commented Oct 30, 2019

Given that we have this in the docs:

class Twitter::API < Grape::API
  error_formatter :txt, ->(message, backtrace, options, env, original_exception) {
    "error: #{message} from #{backtrace}"
  }
end

Would you say that is not enough?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.