gdZddlmZddlmZegdZGddeZGdde Z Gd d ee eZ d S) z flask.views ~~~~~~~~~~~ This module provides class-based views inspired by the ones in Django. :copyright: (c) 2015 by Armin Ronacher. :license: BSD, see LICENSE for more details. )request)with_metaclass)getpostheadoptionsdeleteputtracepatchc6eZdZdZdZdZdZedZdS)ViewaAlternative way to use view functions. A subclass has to implement :meth:`dispatch_request` which is called with the view arguments from the URL routing system. If :attr:`methods` is provided the methods do not have to be passed to the :meth:`~flask.Flask.add_url_rule` method explicitly:: class MyView(View): methods = ['GET'] def dispatch_request(self, name): return 'Hello %s!' % name app.add_url_rule('/hello/', view_func=MyView.as_view('myview')) When you want to decorate a pluggable view you will have to either do that when the view function is created (by wrapping the return value of :meth:`as_view`) or you can use the :attr:`decorators` attribute:: class SecretView(View): methods = ['GET'] decorators = [superuser_required] def dispatch_request(self): ... The decorators stored in the decorators list are applied one after another when the view function is created. Note that you can *not* use the class based decorators since those would decorate the view class and not the generated view function! Nct)zSubclasses have to override this method to implement the actual view function code. This method is called with all the arguments from the URL rule. )NotImplementedError)selfs A/granary/edev/quantum/lib/python3.11/site-packages/flask/views.pydispatch_requestzView.dispatch_requestAs "###cfd|jr(|_|j_|jD] }||_|_|j_|j_|j_S)aConverts the class into an actual view function that can be used with the routing system. Internally this generates a function on the fly which will instantiate the :class:`View` on each request and call the :meth:`dispatch_request` method on it. The arguments passed to :meth:`as_view` are forwarded to the constructor of the class. c8ji}|j|i|S)N) view_classr)argskwargsr class_args class_kwargsviews rrzView.as_view..viewRs1"4?J?,??D(4($9&99 9r) decorators__name__ __module__r__doc__methods)clsnamerr decoratorrs `` @ras_viewz View.as_viewHs : : : : : : : > ' DM!nDO ^ ' '  y { .{  r) rr __qualname__r!r"rr classmethodr&rrrrrsW@GJ$$$[rrceZdZdZdS)MethodViewTypec t||||}d|vrat|jpg}|D]2}|tvr'||3|rt||_|S)Nr")type__new__setr"http_method_funcsadduppersorted)r#r$basesdrvr"keys rr-zMethodViewType.__new__ks \\#tUA . . A  "**++G - -+++KK ,,,  -#G__  rN)rr r'r-rrrr*r*is#     rr*ceZdZdZdZdS) MethodViewaLike a regular class-based view but that dispatches requests to particular methods. For instance if you implement a method called :meth:`get` it means you will response to ``'GET'`` requests and the :meth:`dispatch_request` implementation will automatically forward your request to that. Also :attr:`options` is set for you automatically:: class CounterAPI(MethodView): def get(self): return session.get('counter', 0) def post(self): session['counter'] = session.get('counter', 0) + 1 return 'OK' app.add_url_rule('/counter', view_func=CounterAPI.as_view('counter')) ct|tjd}|!tjdkrt|dd}|Jdtjz||i|S)NHEADrzUnimplemented method %r)getattrrmethodlower)rrrmeths rrzMethodView.dispatch_requestsvtW^1133T:: rCs######IBBBCCSSSSS6SSSlT$%%%%%55%%%%%r