2Bf|ddlZddlmZddlmZegdZGddZGdd eZ Gd d ee Z y) N)request)ResponseReturnValue)getpostheadoptionsdeleteputtracepatchc "eZdZUdZdZej ejee d<dZ ej e e d<gZ ejeje d<defdZeded ej"d ej"dejfd Zy) 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 f"Hello {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! Nmethodsprovide_automatic_options decoratorsreturnct)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 K/var/www/highfloat_scraper/venv/lib/python3.12/site-packages/flask/views.pydispatch_requestzView.dispatch_request=s "##name class_args class_kwargscdtjdtjdtffd |jr1|_|j _|jD] }| |_|_|j_|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. argskwargsrcLji}|j|i|S)N) view_classr)rrrrrviews rr"zView.as_view..viewQs0"4??J?,?D(4(($9&9 9r) tAnyrr__name__ __module__r!__doc__rr)clsrrr decoratorr"s `` @ras_viewz View.as_viewDs : : :3F : >> DM!nnDO ^^ '   ' {{ ..{{ ),)F)F& r)r%r& __qualname__r'rr#OptionalListstr__annotations__rboolrCallablerr classmethodr$r*rrrr s@(,GQZZs $+37qzz$/6&(Jqzz"'$"5$!!%&UU!<=EE! !!rrc"eZdZdZfdZxZS)MethodViewTypezYMetaclass for :class:`MethodView` that determines what methods the view defines. c(t||||d|vr|t}|D]+}t|dds|j |j -t D].}t||s|j|j0|r||_yyy)Nr) super__init__setgetattrupdaterhttp_method_funcshasattraddupper)r(rbasesdrbasekey __class__s rr8zMethodViewType.__init__ns ua( A eG 14D1NN4<<0 1) -3$KK , -%  r)r%r&r+r'r8 __classcell__)rDs@rr5r5is&&rr5cLeZdZdZdej dej defdZy) MethodViewaA class-based view that dispatches request methods to the corresponding class methods. For example, if you implement a ``get`` method, it will be used to handle ``GET`` requests. :: 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')) rrrct|tjjd}| tjdk(r t|dd}|Jdtj||i|S)NHEADrzUnimplemented method )r:rmethodlower)rrrmeths rrzMethodView.dispatch_requestsktW^^113T: rRsE'I ZZz&T&6%%r