feature request: @login_required and @admin_required methods argument about gae-init

[joernhees]

is this really business specific as mentioned in #245? redirects for permissions... maybe, but having world readable but not writable pages seems like a pretty standard thing to me

[bangive]

i like it too

[nazroll]

+1

i don't think the use case would be business specific. rewriting the decorators to support args can help us build a more specific use case endpoints.

[jaxon]

+1

[joenorton]

What's an example of an argument you'd want to pass in? I want to better understand this.

You do know you can utilize variables in your route's inside the decorator, as-is, right? And that won't do the trick?

Here's an example decorator - where I am pulling the 'account_id' from the route and using it in the decorator:

def account_required(f):
    def account_decorator(f):
        decorator_order_guard(f, 'auth.account_required')

    @functools.wraps(f)
    def decorated_function(*args, **kws):
        account_id = kws['account_id']
        if current_user_account() == account_id:
            return f(*args, **kws)
        return flask.redirect(flask.url_for('account_list'))
    return decorated_function

[topless]

Just to add my 3.14 cents here, although kind of late, but just in case anyone stumbles on it. I am using mr. norton's approach looking in the request like

if 'my_variable' in kws: do_stuff()

For handling logic I would suggest to use the API section where you can actually decorate the methods you desire. Use control/ only for server side rendering.

[lipis]

I'll pass on this one.. Also @topless idea could work :)