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
Namespace takes an api argument, i.e. ns1 = Namespace(api=api, ...). However, this is not enough to make sure the namespace is automatically documented in swagger.json`; for that to work, the namespace needs to be expclicitly added to the api, i.e.
api.add_namespace(ns1)
Wouldn't it make sense to do this automatically when Namespace is instantiated with an api argument?
The text was updated successfully, but these errors were encountered:
There's definitely redundancy in relating APIs and Namespaces. While it seems like a small thing, a change in how this works could be fairly disruptive to current users, depending on implementation and messaging around the change. Will spread this around to other maintainers.
Namespace
takes anapi
argument, i.e.ns1 = Namespace(api=api, ...). However, this is not enough to make sure the namespace is automatically documented in
swagger.json`; for that to work, the namespace needs to be expclicitly added to the api, i.e.Wouldn't it make sense to do this automatically when
Namespace
is instantiated with anapi
argument?The text was updated successfully, but these errors were encountered: