-
Notifications
You must be signed in to change notification settings - Fork 102
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: show more data (in an embeded way) #455
Conversation
react-tooltip helps to implement the feature that when users hovering on certain elements there will be tooltips showing up and presenting anything we want. |
Hi, @frank-zsy, I have some confusion about the data: The json file: I know the number of fork event is not equal to the number of fork, but how to explain the numbers show in the screenshot above? Why there is a huge gap? Are unfork events counted into fork events? |
So cool!! |
@tyn1998 I think the data is not right, I will check it. |
I see, I put the data in wrong key, right now, the data in |
And I think line chart can be used instead of bar chart which is more common in fork and star trending. |
If you are going to use hover to trigger the charts, please make sure that the mouse cursor can easily enter the chart and keep the charts showing so users can dive into the data. This may involve enlarge the detection fields of each charts. I am not sure how to implement it but I think I expressed what I want. |
Hah~got it.
emm, the value of each month represents increment (i.e. 300 fork events ≈ 300 new fork), right? I considered line chart first but turned to bar chart since I thought "trending" required total number rather icrement number. But I can add a line to existing bars so we can present them all in one chart.
Sure, I have considered this. The hover-triggered box can be entered. |
The data update process should be completed by tomorrow morning and the data will be updated to 2022.8 |
Hi @frank-zsy, this is how a line chart looks like: and its bar chart counterpart: or a combination of both: Which way do you prefer? I'm ok with all of them but mildly incline to the combination chart :) How about you guys? @will-ww @wxharry BTW, if we adopt line charts, I need to insert "zero" data for those months without a single event because of: |
I think combination version is better, but what I like is that use bar chart to show the increase value of each month and use line chart to show the accumulate value of all history. |
Ok, I will implement it and update my progress here~ |
But there is a problem that the accumulate value is not accurate since the data is from log events rather than API. So the users may feel quite confused and need to explain the difference. So we need to decide whether to add the accumulate line chart since it may cause extra cost of explanation. |
* refactor: remove antv * refactor: remove all `graphType` or `GraphType` from codebase Co-authored-by: Lam Tang <tangyenan@gmail.com>
fac0f04
to
c4ac0c8
Compare
Finish basic version: add-more-data.mov-8mb.mp4 |
@wxharry Thank your for yor appreciation!
Agree. Actually I tried, but it was so hard for me to decide on the use of plural forms. Could you help? Another limitation is that Echarts doesn't provide an option to center the title text so if users want to center the title text they should adjust
Agree. But they cannot be long since the width of the chart is limited. Docs are good and some hover-to-show features also make sense (support in future). |
IMO, using plural form for all titiles is fine.
Maybe use one word for each legend? Since we have a detailed title, it would be easy for users to understand what that is. |
Also, I noticed that there is a code frequency section in insight tab, which looks similiar to one of our graphs. Are these the same? |
Not the same. Our data only count code line changes after PR merge, while the GitHub counterpart might also include code line changes made by direct push. |
chore: modify chart titles and legends
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
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.
Hi @wxharry, please review and approve :)
/approve |
Brief Information
This pull request is in the type of:
Related issues:
Details
This illustration shows what we want to achieve:
Subtasks:
Checklist
Others