Repository navigation
Add a user settings page for cross-page UI defaults - #70687
Merged
Merged
Conversation
boring-cyborg
Bot
added
area:translations
area:UI
Contributor
|
This is great! We do have light/dark mode, timezone and language exist outside of this. i think it still makes sense to make those quickly accessible and this is for "Advanced" settings. |
1 task done
pierrejeambrun
force-pushed
the
ui-user-settings-panel
branch
from
August 10, 2026 10:31
74cb0ac to
eec2fdc
Compare
pierrejeambrun
marked this pull request as ready for review
August 10, 2026 10:54
pierrejeambrun
requested review from
bbovenzi,
choo121600,
guan404ming,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
August 10, 2026 10:54
Several cross-page UI behaviors have no single place to set a personal default. Graph layout direction and dependency scope are remembered per-Dag, and the clear / mark-as dialog selections reset to a fixed choice every time, so users re-apply the same options over and over. Centralizing these as browser-local preferences lets a user set their default once and have the individual features fall back to it.
pierrejeambrun
force-pushed
the
ui-user-settings-panel
branch
from
August 10, 2026 15:48
eec2fdc to
fa689d9
Compare
bbovenzi
approved these changes
Aug 11, 2026
dabla
pushed a commit
to dabla/airflow
that referenced
this pull request
Aug 14, 2026
Several cross-page UI behaviors have no single place to set a personal default. Graph layout direction and dependency scope are remembered per-Dag, and the clear / mark-as dialog selections reset to a fixed choice every time, so users re-apply the same options over and over. Centralizing these as browser-local preferences lets a user set their default once and have the individual features fall back to it.
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Sep 11, 2026
Several cross-page UI behaviors have no single place to set a personal default. Graph layout direction and dependency scope are remembered per-Dag, and the clear / mark-as dialog selections reset to a fixed choice every time, so users re-apply the same options over and over. Centralizing these as browser-local preferences lets a user set their default once and have the individual features fall back to it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a browser-local Settings page (reachable from the user menu) that gathers cross-page UI defaults in one place. Several of these behaviors had no way to set a personal default before: graph layout direction and dependency scope are remembered per-Dag, and the clear / mark-as dialog selections reset to a fixed choice on every action, so users kept re-applying the same options.
Each preference is stored in
localStorageonly (no server-side profile) and is consumed as a fallback — a per-Dag or per-action choice still overrides it.Settings included:
The redundant "Default to graph/grid view" quick-toggle is removed from the user menu — that preference (
default_dag_view) is already set by the on-page grid/graph switcher, so the menu item was duplicative.Screenshots:
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines