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.

This isn't a code-related issue, but a request to clarify email confirmation flows and endpoints in the documentation. I'd be happy to submit a pull request for this, but I need more information about how this is expected to work, before I'll be able to explain it. There's also related code that's been merged but not released yet (specifically: https://github.com/lynndylanhurley/devise_token_auth/

Provide a mock show page that will allow users to view a mock configuration with a legit layout.

• Use code formatting for body content & script
• Description links should be rendered as link, not as text

When I would like to use Simple Token Authentication
But the gem doesn't quite fit my use case
I want be told about alternatives
So that I can understand the trade-offs that were made
And decide if I prefer creating a pull request or use another of the tools that are available

When I maintain a gem that provides token authentication using Devise
I want t

Error Messages

Coverage report generated for RSpec to /mnt/c/Users/b9990/Documents/GitHub/compassbioinfo/good_will_mina_api/coverage. 1125 / 1181 LOC (95.26
%) covered.
SimpleCov failed with exit 1
Traceback (most recent call last):
        45: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/rspec-core-3.9.1/exe/rspec:4:in `<main>'
        44: from /home/khiav/.rvm/gems/ruby-2.5.5/gems/r

While there is support in the Ruby code for the Streaming API, the docs are completely empty. We should fix that by filling them in. Anyone want to help?

I am trying to create documentation for this

    desc 'Returns your public timeline.' do
    summary 'summary'
    detail 'more details'
    named 'My named route'
    headers XAuthToken: {
              description: 'Validates your identity',
              required: true
            },
            XOptionalHeader: {
              description: 'Not really needed',
           

If you PATCHed to /posts/1, but send payload with a different id:

{
  data: {
    id: 789,
    type: 'posts',
    attributes: { ... }
  }
}

We pay attention to the payload and not the URL - instead let's throw an error when there is a mismatch.

my app's page params are in the url

things_path(page: 2) # => "/things/page/2"

not

things_path(page: 2) # => "/things?page=2"

however, the generated links use this second form, which appears to be hardcoded in Pagination#_paginate_collection

When getting the value of a key it is not possible to get all attributes.
It might be useful to get the session for example in the case that it is needed to discover a leader.

Hi there,
I do find the default values for jsonapi_cache and default initializers, but is it possible to add some documentation? I have a very static json and it would be awesome to have it cached somewhere.
Thanks in advance!

There should be documentation on how to interface with you software : what is the format out of the command line, if a JSON format is used, please describe it, this will ease the integration with other software, for example : Kresus (kresus.org), a libre self hosted account manager.
In addition, a command to list all the accounts (with IBAN + account label + balance) would also help into going th