o j2@sddlmZddlZddlmZddlmZddlmZej dej dej fd Z e gd ZGd d d ZGd ddeZdS)) annotationsN)typing) current_app)requestF.)bound)getpostheadoptionsdeleteputtracepatchc@sZeZdZUdZdZded<dZded<gZded<d Zd ed <dddZ e dddZ dS)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``. Nz$t.ClassVar[t.Collection[str] | None]methodszt.ClassVar[bool | None]provide_automatic_optionsz(t.ClassVar[list[t.Callable[..., t.Any]]] decoratorsTzt.ClassVar[bool]init_every_requestreturnft.ResponseReturnValuecCst)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. )NotImplementedErrorselfr~/root/aizidognhua/tmp/workspace/projects/ec89d86c-575f-41c9-af57-ac45cbdbf775/venv/lib/python3.10/site-packages/flask/views.pydispatch_requestNszView.dispatch_requestnamestr class_argst.Any class_kwargsft.RouteCallablecs|jr d fdd n|id fdd |jr/|_|j_|jD]}|q(|_|_|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. kwargsr!rrcs&ji}t|jdi|SNr) view_classr ensure_syncr)r$r)r r"viewrrr(js zView.as_view..viewcstjdi|Sr%)rr'r)r$rrrr(ssNr$r!rr)rr__name__ __module__r&__doc__rr)clsrr r" decoratorr)r r"rr(ras_viewUs   z View.as_view)rr)rrr r!r"r!rr#) r*r+ __qualname__r,r__annotations__rrrr classmethodr/rrrrrs  "   rcs,eZdZdZd fdd Zd d d ZZS) 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$r!rNonec s~tjdi|d|jvr;t}|jD]}t|ddr"||jqtD]}t ||r3| | q%|r=||_dSdSdS)Nrr) super__init_subclass____dict__set __bases__getattrupdaterhttp_method_funcshasattraddupper)r-r$rbasekey __class__rrr6s       zMethodView.__init_subclass__rcKs\t|tjd}|durtjdkrt|dd}|dus$Jdtjt|di|S)NHEADr zUnimplemented method r)r:rmethodlowerrr')rr$methrrrrs  zMethodView.dispatch_request)r$r!rr4r))r*r+r0r,r6r __classcell__rrrBrr3sr3) __future__rrtftglobalsrrTypeVarCallableAnyr frozensetr<rr3rrrrs    z