It works very well. For Superset (aka Caravel) we're mostly in the React / async world while using FAB as an async REST backend, and still leveraging the CRUD interface where it makes sense. It's nice to be able to define roles as collection of perms that affect both the REST api and the UI consistently.
Note that it's also common to have a data injection point to pass "bootstrap data" along with the simple html container that is sent over, usually squishing a json blob somewhere in the static dom. Barebone templating work well for that. On Mon, Nov 28, 2016 at 4:27 PM, Li Xuan Ji <xua...@gmail.com> wrote: > Max, > > How well does FAB support building pages that use XHR to consume a > REST api, instead of doing templating on the backend? > > We already have some ad-hoc XHR in airflow, and backend templating is > the reason large DAG graph/tree views don't render (and probably other > things I missed). It might be good to move away from backend > templating completely for consistency. > > Regards, > Xuanji > > > On 28 November 2016 at 19:14, Maxime Beauchemin > <maximebeauche...@gmail.com> wrote: > > Glad to see this! On my side I've been playing around trying to use Flask > > App Builder (just obtained committer status on the project) which covers > > some out of the box CRUD REST API for models and a > > authentication/role/permission framework that would allow for a > > multi-tenant UI / API with arbitrary roles / granular access. > > > > We should chat as to how these solutions might work together. My early > work > > and some of the rational for it can be found here: > > https://github.com/mistercrunch/airflow_webserver > > > > We should chat! Let's schedule time. > > > > Max > > > > On Mon, Nov 28, 2016 at 11:36 AM, Andrew Phillips <andr...@apache.org> > > wrote: > > > >> Just wanted to say this is very exciting, thank you Bolke :). > >>> > >> > >> Big +1 to that. Thanks, Bolke! > >> > >> ap > >> > > > > -- > Im Xuan Ji! >
