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
a MethodViewResolver that works specifically with flasks method views
In both cases, the class args and kwargs should be passed inside the resolver to allow for dependency injection.
Perhaps somewhere it should be documented that for the MethodResolver a single instance is used across all requests while with the MethodViewResolver, as the result of the as_view behaviour, a new instance is created for each request. This could help to avoid pitfall regarding thread safety.
The text was updated successfully, but these errors were encountered:
It would be nice to have both:
MethodResolver
that works with any classMethodViewResolver
that works specifically with flasks method viewsIn both cases, the class
args
andkwargs
should be passed inside the resolver to allow for dependency injection.Perhaps somewhere it should be documented that for the
MethodResolver
a single instance is used across all requests while with theMethodViewResolver
, as the result of the as_view behaviour, a new instance is created for each request. This could help to avoid pitfall regarding thread safety.The text was updated successfully, but these errors were encountered: