Dynamic matching / static matching - expected behaviour

When trying to have an endpoint that matches dynamically except for specific keywords.
i.e.
GET resource/:id => returns the resource
GET resource/new => returns a JSON schema of the resource

The issue is that when I define it this way:

class ResourceAPI
  get 'resource/:id' do
    # ...
  end

  get 'resource/new' do
    # ...
  end
end

I will never hit the resource/new endpoint. However, if I define it the other way around, it will work.

Start by reproducing the route definitions shown in the issue and inspect Grape's endpoint matching and declaration-order behavior. Confirm whether a static resource/new route can take precedence over resource/:id regardless of definition order; done means both routes resolve to their intended handlers, with regression coverage for the example.