Passing User Data into Dash App

[DanielHHowell]

Thanks so much for this great work!

I've got everything running perfectly, but one hurdle I am trying to overcome is how to pass the current user into the dash app. I realize it's instantiated through login_required(), and would generally use current_user.username or store it in a session['username'] but can't figure out how to do it in this case. Any pointers for this?

Much thanks in advance!

[okomarov]

Can you give a code snippet?

The views are protected with a login_required already and the dashapps are instantiated with flask's context, so you should just be able to import the current_user.

[DanielHHowell]

Thanks for the quick reply. So something like this:

from flask import session
from flask_login import login_required, current_user
import dash
import dash_core_components as dcc
import dash_html_components as html
from dash.dependencies import Input, Output
# Import factory method
from app import create_app

def protect_dashviews(dashapp):
    for view_func in dashapp.server.view_functions:
        if view_func.startswith(dashapp.config['url_base_pathname']):
            dashapp.server.view_functions[view_func] = login_required(dashapp.server.view_functions[view_func])

# Create Flask server app
server = create_app()

# Create dash app passing our server
dashapp = dash.Dash(__name__, server=server, url_base_pathname='/dashboard/')
protect_dashviews(dashapp)

with server.app_context():

    dashapp.layout = html.P(str(current_user.username))

The current_user object passed is None so all the attributes are also inaccessible.

[okomarov]

First thing that jumps to the eye is that this solution is missing the login_required user loader.

Have you tried using the code from this repo as a template and pick the things that you need by deleting from it rather than composing? I am afraid I won't be able to support composable patterns as there are simply too many moving parts (which was the motivation for this template in the first place).

[DanielHHowell]

I think the problem was that there was a new server instance, so the previous current_user couldn't be sent. For others searching, I found the dash-auth-flow repo more suited for this particular purpose.

[sorenwacker]

I have the same question.

[okomarov]

@sorenwacker I've addressed this in the latest commit https://github.com/okomarov/dash_on_flask/commit/9066685b14a683085ce78a8b327ce33d20493082 which was a response to https://github.com/okomarov/dash_on_flask/issues/21