You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
recently got error :
in lib/grape-swagger.rb:96:in setup': undefined methodmerge!' for nil:NilClass (NoMethodError)
in create_documentation_class:setup
the culprit is line
@last_description.merge!(api_doc)
I don't know what changed, but would it be safer to initialise @last_description to an empty hash
before merging, in case this member is not previously set properly / as expected ?
note : after making some safe guard I got other errors, in mounting API.
But after debugging, it seems that there is ongoing PR that aren't completed around removing Endpoint.settings.
def combine_namespaces(app)
app.endpoints.each do |endpoint|
ns = endpoint.settings.stack.last[:namespace]
where settings is no longer a member of an Endpoint.
So I guess, this is not a grape-swagger issue, but a transient problem around this unfinished PR.
This has probably been introduced in ruby-grape/grape#739 on Grape/HEAD. Grape-swagger "knows" about some Grape internals, we need to refactor our way of that into using a more standard interface.
recently got error :
in lib/grape-swagger.rb:96:in
setup': undefined method
merge!' for nil:NilClass (NoMethodError)in create_documentation_class:setup
the culprit is line
I don't know what changed, but would it be safer to initialise @last_description to an empty hash
before merging, in case this member is not previously set properly / as expected ?
note : after making some safe guard I got other errors, in mounting API.
But after debugging, it seems that there is ongoing PR that aren't completed around removing Endpoint.settings.
where settings is no longer a member of an Endpoint.
So I guess, this is not a grape-swagger issue, but a transient problem around this unfinished PR.
see here : ruby-grape/grape#712 and ruby-grape/grape#719
reverting to Grape 0.9.0 work.
Good luck for the upgrade ;-)
The text was updated successfully, but these errors were encountered: