GitHub user pykenny edited a discussion: User-level (and persisted) UI configuration
TL;DR: Looking up possibility of introducing user-level Web-UI configuration in future release. Recently I was checking out the idea behind the option to hide datasets (will be "assets" in 3.x) in graph view, which is introduced in 2.10: - https://github.com/apache/airflow/issues/41003 I'm having similar trouble when looking up several DAGs I'm working with. Having the option available is helpful for searching in the graph view, but now I have to toggle them each time I reenter the graph view of these DAGs. From the original proposal adding global configuration to set up default behavior was another possible approach, but doing that globally comes up with another issue: what if my coworkers doesn't think so? Maybe they don't work on DAGs with huge amount of datasets that often, and feel dataset links pretty helpful when looking up other graphs? Another case I can think of which requires user-level customization is default behavior when entering homepage (`/home`) of web UI. By default Airflow (2) seems to memorize tab/filters in user session, and let users start from where they ended up with. I feel that disturbing because seeing "All" or "Active" tab with all filters clears makes much more sense to me when I enter the homepage fresh on the next workday, instead of seeing just 1-2 DAGs remain, feeling very surprised and having to tell myself always remember to reset tab/filters (or, log out !?) when closing the tab. Again, perhaps most Airflow users, including my coworkers, feel more natural about that and don't think that annoying at all! Up to now, Airflow 2 offers (at least, maybe?) two potential ways to customize UI behavior: - Global configuration, which applies to all users directly - Session-based user settings, which doesn't persist in user account, or to say not available through API/Backbone DB And user configuration page allows customizing two settings (`/users/userinfo`) and nothing else if one's not in "Admin" role: - Displayed name - Password Hence I think making part of the Web UI settings adjustable/customizable at user account level, and persist these settings through API/Backbone DB may help improving user experience on Web UI usage, and getting more consistent experience when some global UI configuration change is made by service administrators. GitHub link: https://github.com/apache/airflow/discussions/46708 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
