-
Notifications
You must be signed in to change notification settings - Fork 96
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
feat: create research route #307
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.
Great Job ,Looks amazing 💯
I have some minor comments if you would like to change.
src/pages/DataResearch.tsx
Outdated
return ( | ||
<PageContainer> | ||
<Widget> | ||
<h1>מחקרים</h1> |
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 should use here useTranslation and not Hebrew
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.
it's a temporary internal thing, I don't think it should ever be translated
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.
Ok, I understand
src/pages/DataResearch.tsx
Outdated
|
||
return ( | ||
<Widget> | ||
<h1>בעיות etl/gps/משהו גלובאלי אחר</h1> |
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.
Also here and in some more places in this file , pls use useTranslation
src/pages/DataResearch.tsx
Outdated
) | ||
} | ||
|
||
function StackedResearchSection() { |
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 should move it above the DataResearch component
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?
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.
As I wrote in different comment you don't have to
src/pages/DataResearch.tsx
Outdated
) | ||
} | ||
|
||
function StackedResearchInputs({ |
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 should move it above the StackedResearchSection component
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?
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.
Hmm, you don't have to, but when I read the file from above to down you use functions and then declare them. However, you use the component in different file so it is not give an errors, up to you.
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.
Usually, I prefer putting helper function and small utilities at the bottom, so when you read it you'll see the important things first.
But it's just an opinion
https://softwareengineering.stackexchange.com/questions/196997/helper-methods-placement
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.
Ok 👍
In addition, I think we should have an option to choose the list of operators/exclude some of them it will help in extracting data, in my opinion, but it is for another issue. |
src/pages/DataResearch.tsx
Outdated
<Grid xs={6} item> | ||
<DateSelector | ||
time={endDate} | ||
onChange={(data) => setEndDate(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.
Suggestion: It is better not to allow to choose an end date earlier than the start date
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're right, but since it's an internal endpoint, it's less important here.
However, it is a great idea to open an issue to fix that on the front page
Thanks for the review,
|
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.
Only, one suggestion, if you want of course. Make the tooltip in a height of the chart and scroll-able.
You also can leave it as it is :)
Great Work 👍
thanks @ArkadiK94 ! |
Thanks @NoamGaash that's amazing! |
@ArkadiK94 - Agreed. I'll open an issue on that |
Description
add a research secret route with stacked chart
solve #261 and #262
screenshots