variable scope in Grape versioned-controller

Hello,
I have been using Grape to build an API within an already-existing Rails project.
I have been dealing with an error that I do not understand and I wonder if somebody could draw some light on this as it could be a bug but I am not sure.

My colleague and I were tasked with creating 4 end-points for this API:

• /packages
• /packages/:id
• /options
• /options/:id

This is what my colleague wrote (which works perfectly!):

module API
  class V1::Package < Grape::API
    get '/packages/:id' do
      @package = ::Package.find_by(id: params[:id])
      render rabl: 'v1/packages/show'
    end

    get '/packages' do
      @packages = ::Package.all
      render rabl: 'v1/packages/index'
    end
  end
end

And this is what I wrote (basically the exact same, but for options):

module API
  class V1::Option < Grape::API
    get '/options/:id' do
      @option = ::Option.find_by(id: params[:id])
      render rabl: 'v1/options/show'
    end

    get '/options' do
      @options = ::Option.all
      render rabl: 'v1/options/index'
    end
  end
end

The first end-point (/options/:id) works but the second one throws an error.

  API::V1::Option GET /api/v1/options/ returns all options
     Failure/Error: get '/api/v1/options'

     TypeError:
       no implicit conversion of Symbol into Integer

This is because basically @options is expected to be a Hash and not an Array (or ActiveRecord::Relation). Further debugging made me discover that using a different variable (something other than @options) fixed the issue!

But why is this?

In the first example (my colleague's code), @packages is set to nil before being set to whatever we set it to. But in my case @options was assigned to:

{
                   :method => [
        [0] "GET"
    ],
                     :path => [
        [0] "/options"
    ],
                      :for => API::V1::Option < Grape::API,
            :route_options => {
        :params => {}
    },
    :options_route_enabled => true
}

and (re-)assigning it to an array, a collection or an ActiveRecord::Relation broke the code. For now, I'll just re-name my variable to something else but I'd love to hear somebody else's opinion on this as I don't think this behaviour is expected.

Start by reproducing the GET /api/v1/options failure from the issue, comparing the API::V1::Package and API::V1::Option Grape::API definitions. Inspect how the /options route and its render rabl target use @options, then verify that the endpoint works with the intended collection value and that the existing package endpoints remain unaffected.