Skip to content
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

Merged
merged 9 commits into from
Dec 16, 2023
Merged

feat: create research route #307

merged 9 commits into from
Dec 16, 2023

Conversation

NoamGaash
Copy link
Member

@NoamGaash NoamGaash commented Dec 15, 2023

Description

add a research secret route with stacked chart
solve #261 and #262

screenshots

image
image

@ArkadiK94
Copy link
Collaborator

image
as you can see the table is overflow to next chart.
In addition, please, sort the data in every chart by name/amount so it will be easier to find what we look for, by name-> to find the operator, by amount --> to see the worst/better performance

@ArkadiK94
Copy link
Collaborator

image
Could you make the inputs smaller as in other parts of the website?

Copy link
Collaborator

@ArkadiK94 ArkadiK94 left a 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.

return (
<PageContainer>
<Widget>
<h1>מחקרים</h1>
Copy link
Collaborator

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

Copy link
Member Author

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

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I understand


return (
<Widget>
<h1>בעיות etl/gps/משהו גלובאלי אחר</h1>
Copy link
Collaborator

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/routes/index.tsx Show resolved Hide resolved
src/routes/index.tsx Outdated Show resolved Hide resolved
)
}

function StackedResearchSection() {
Copy link
Collaborator

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why?

Copy link
Collaborator

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

)
}

function StackedResearchInputs({
Copy link
Collaborator

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why?

Copy link
Collaborator

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.

Copy link
Member Author

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

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok 👍

@ArkadiK94
Copy link
Collaborator

ArkadiK94 commented Dec 16, 2023

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.

<Grid xs={6} item>
<DateSelector
time={endDate}
onChange={(data) => setEndDate(data)}
Copy link
Collaborator

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

Copy link
Member Author

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

@NoamGaash
Copy link
Member Author

NoamGaash commented Dec 16, 2023

Thanks for the review,

  • regarding sorting - that's out of scope for this PR, we can do it in the future.
  • z-index - fixed.
  • Smaller inputs & sorting - well, it's an internal endpoint for research purposes, so I don't want to spend time on making it visually appealing. if anyone wants to improve the design, it can be done on future pull requests.

@NoamGaash NoamGaash requested a review from ArkadiK94 December 16, 2023 10:16
Copy link
Collaborator

@ArkadiK94 ArkadiK94 left a 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 👍

@NoamGaash
Copy link
Member Author

NoamGaash commented Dec 16, 2023

thanks @ArkadiK94 !
that's a great suggestion, but I'm not sure it's possible using rechart built-in components. The tooltip can't be hovered, therefore I don't see how can it be scrolled

@NoamGaash NoamGaash merged commit 244b222 into main Dec 16, 2023
13 checks passed
@NoamGaash NoamGaash deleted the feat/research-route branch December 16, 2023 10:51
@ShayAdler
Copy link
Collaborator

Thanks @NoamGaash that's amazing!

@ShayAdler
Copy link
Collaborator

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.

@ArkadiK94 - Agreed. I'll open an issue on that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a research stack bar with all the operators execution rate Create a secret route /data-research
4 participants