-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DAG list sorting lost when switching page #29756
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to test your feature locally before sending that for a review as 'ready to merge' so you are sure this actually solves the problem. You can take a look at these guides to setup your local environment for development:
- https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst
- https://github.com/apache/airflow/blob/main/CONTRIBUTORS_QUICK_START.rst
If the PR is not ready you can mark is a 'draft' while waiting for feedback.
For this particular case, you can take a look at one specific query param that we are handling, for instance 'search' and look how it's done.
(generate_pages now takes those 2 extra args but do nothing with them, look at get_params
).
Looking better!
|
Thank you for the review @bbovenzi |
* Adding sorting keys to generate_pages * Handling review comments and using the new keys * Fixing Brent review comments * Adding docstring --------- Co-authored-by: Amogh <[email protected]> (cherry picked from commit c8cd90f)
* Adding sorting keys to generate_pages * Handling review comments and using the new keys * Fixing Brent review comments * Adding docstring --------- Co-authored-by: Amogh <[email protected]> (cherry picked from commit c8cd90f)
The dag list sorting order is lost on changing the pages. We should persist the key across pagination
closes: #29322
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.