Parameterise key sorting in "Rendered Template" view
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Description
Currently the https://github.com/apache/airflow/blob/main/airflow/www/views.py#L1254 has forceful sorting by keys.
It'd be very nice to have this behaviour parameterised and not hardcoded
### Use case/motivation
Sometimes we have big templates with few nested levels and it's very inconvenient to see higher level keys scattered across few screens located at the very bottom of template despite initially it was on the very start just because it was sorted by key forcefully.
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
Research direction
Start in airflow/www/views.py around line 1254, where the Rendered Template view currently sorts keys forcefully. Read the surrounding view logic to determine how sorting can be exposed as a parameter without losing the existing behavior. Done means higher-level keys can remain in their original order when requested instead of always being sorted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100