ryanahamilton commented on pull request #12365: URL: https://github.com/apache/airflow/pull/12365#issuecomment-728140794
I know it seems harmless, but I don't love the idea of using a config flag to determine this behavior. The accumulation of these types of "opt-in features" will contribute to a more fragmented overall product experience IMO. Just thinking out loud, maybe the `flask_session` could be utilized to store the last toggle state on a per-user basis? I do wonder if collapsing it by default could be an acceptable experience for everyone if we updated the presentation to stand out a bit more (like the mock below)? This would certainly be the easiest solution, but I'd be interested to get others' opinions on this.  ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
