-
Notifications
You must be signed in to change notification settings - Fork 33
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
fix(orchestrator):implement filters #386
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Lior Soffer <[email protected]>
Changed Packages
|
|
const currentDate = new Date(); | ||
const endOfToday = new Date(currentDate); | ||
endOfToday.setHours(23, 59, 59, 999); | ||
|
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.
If I'm not wrong, new Date()
uses the tz in which the system is running. Can you please double check if it's ok?
what if the user tz is different from system tz?
} | ||
return undefined; | ||
}, [statusSelectorValue, workflowId]); | ||
return filters[0] || undefined; |
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 filters[0]
? can't be there more than one valid filter?
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.
This looks good to me since if (filters.length > 1)
above handles that case
<Selector | ||
label="Status" | ||
items={statuses} | ||
onChange={value_ => { |
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.
onChange={value_ => { | |
onChange={value => { |
<Selector | ||
label="Started" | ||
items={started} | ||
onChange={value_ => { |
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.
Likewise. Please check other occurrences of this pattern as well.
} | ||
return undefined; | ||
}, [statusSelectorValue, workflowId]); | ||
return filters[0] || undefined; |
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.
This looks good to me since if (filters.length > 1)
above handles that case
resolve FLPATH-1989
Screencast.from.2025-02-04.19-10-12.mp4