-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Store grid view selection in url params #23290
Conversation
CC: @staufferl16 |
@@ -27,5 +27,8 @@ export default function useTasks(dagId) { | |||
return useQuery( | |||
['tasks', dagId], | |||
() => axios.get(tasksUrl), | |||
{ | |||
placeholderData: { tasks: [] }, |
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.
Is this argument a default return value for the useQuery
function?
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.
Yes, but it doesn't affect the cache https://react-query.tanstack.com/guides/placeholder-query-data
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.
Router/search param code looks great to me! I've been using MemoryRouter for tests too.
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.
LGTM 👍
@@ -42,13 +42,13 @@ const Wrapper = ({ children }) => { | |||
<ContainerRefProvider value={{}}> | |||
<TimezoneProvider value={{ timezone: 'UTC' }}> | |||
<AutoRefreshProvider value={{ isRefreshOn: false, stopRefresh: () => {} }}> | |||
<SelectionProvider value={{ onSelect: () => {}, selected: {} }}> | |||
<MemoryRouter> |
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.
Why do we use MemoryRouter here but BrowserRouter elsewhere?
Does MemoryRouter mean that components here don't change the URL, right?
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.
Oh. This is a test.jsx
:D
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.
Yes, tests aren't run on an actual browser so we use a different router.
The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
* Add url params for dag_run_id and task_id * Persist other search params * simplify useSelection * delete extra params * remove API change (cherry picked from commit 4c1fcee)
* Add url params for dag_run_id and task_id * Persist other search params * simplify useSelection * delete extra params * remove API change (cherry picked from commit 4c1fcee)
Store the selected dag run and task instance with
dag_run_id
andtask_id
url params for Grid view.This allowed us to simplify
useSelection
to no longer need useContext. Then I moved some non-components from/tree
to/tree/utils
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 newsfragement file, named
{pr_number}.significant.rst
, in newsfragments.