FdmddlZddlmZddlmZddlmZegdZGddZ Gd d e Z dS) N)typing) current_app)request)getpostheadoptionsdeleteputtracepatchc beZdZUdZdZejejeje e d<dZ ejeje e d<gZ ejejeje d<dZeje e d<dejfd Zed e d ejd ejdejfd ZdS)ViewaSubclass this class and override :meth:`dispatch_request` to create a generic class-based view. Call :meth:`as_view` to create a view function that creates an instance of the class with the given arguments and calls its ``dispatch_request`` method with any URL variables. See :doc:`views` for a detailed guide. .. code-block:: python class Hello(View): init_every_request = False def dispatch_request(self, name): return f"Hello, {name}!" app.add_url_rule( "/hello/", view_func=Hello.as_view("hello") ) Set :attr:`methods` on the class to change what methods the view accepts. Set :attr:`decorators` on the class to apply a list of decorators to the generated view function. Decorators applied to the class itself will not be applied to the generated view function! Set :attr:`init_every_request` to ``False`` for efficiency, unless you need to store request-global data on ``self``. Nmethodsprovide_automatic_options decoratorsTinit_every_requestreturnct)zThe actual view function behavior. Subclasses must override this and return a valid response. Any variables from the URL rule are passed as keyword arguments. )NotImplementedError)selfs TC:\Users\ChattiNader\Documents\MyHotelMatch\api\dev\Lib\site-packages\flask/views.pydispatch_requestzView.dispatch_requestKs "###name class_args class_kwargsc|jr!dtjdtjffd n&|idtjdtjffd |jr(|_|j_|jD] }||_|_|j _ |j_|j _ |j _ S)afConvert the class into a view function that can be registered for a route. By default, the generated view will create a new instance of the view class for every request and call its :meth:`dispatch_request` method. If the view class sets :attr:`init_every_request` to ``False``, the same instance will be used for every request. Except for ``name``, all other arguments passed to this method are forwarded to the view class ``__init__`` method. .. versionchanged:: 2.2 Added the ``init_every_request`` class attribute. kwargsrc\ji}tj|jdi|SN) view_classr ensure_syncr)r rrrviews rr&zView.as_view..viewgsH&t#/F{.t/DEEOOOOOrcBtjjdi|Sr")rr%r)r rs rr&zView.as_view..viewps'E{.t/DEEOOOOOr) rtAnyftResponseReturnValuer__name__ __module__r$__doc__rr)clsrrr decoratorrr&s `` @@ras_viewz View.as_viewRs%&  ! P Pqu P)? P P P P P P P P P3 3l33D Pqu P)? P P P P P P > ' DM!nDO ^ ' '  y { .{ ),)F& r)r,r- __qualname__r.rr(ClassVarOptional Collectionstr__annotations__rboolrListCallablerr*r+r classmethodr) RouteCallabler1r#rrrr s D:>GQZ 1<#45 6=== ?Cqz!*T*:;BBB24J 16!*-.333,0 4(///$""8$$$$11%&U1<=E1 111[111rrcZeZdZdZdejddffd ZdejdejfdZ xZ S) MethodViewaDispatches request methods to the corresponding instance methods. For example, if you implement a ``get`` method, it will be used to handle ``GET`` requests. This can be useful for defining a REST API. :attr:`methods` is automatically set based on the methods defined on the class. See :doc:`views` for a detailed guide. .. code-block:: python class CounterAPI(MethodView): def get(self): return str(session.get("counter", 0)) def post(self): session["counter"] = session.get("counter", 0) + 1 return redirect(url_for("counter")) app.add_url_rule( "/counter", view_func=CounterAPI.as_view("counter") ) r rNc ntjdi|d|jvrt}|jD]-}t |ddr||j.tD]9}t||r'| | :|r ||_dSdSdS)Nrr#) super__init_subclass____dict__set __bases__getattrupdaterhttp_method_funcshasattraddupper)r/r rbasekey __class__s rrAzMethodView.__init_subclass__s!!++F+++ CL ( (eeG  1 14D111NN4<000( - -3$$-KK ,,, &%  ) ( & &rc t|tjd}|!tjdkrt|dd}|Jdtjt j|di|S)NHEADrzUnimplemented method r#)rErmethodlowerrr%)rr meths rrzMethodView.dispatch_requeststW^1133T:: r>s~4&&4&&&&&&" 7 723I 7 7 7 7 7 7 7 7rr>) rr(r*globalsrr frozensetrGrr>r#rrrWs IIII wwwwwwwwt57575757575757575757r