-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Add color scale setting #632
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #632 +/- ##
==========================================
+ Coverage 69.07% 69.39% +0.31%
==========================================
Files 35 35
Lines 2393 2369 -24
==========================================
- Hits 1653 1644 -9
+ Misses 740 725 -15 ☔ View full report in Codecov by Sentry. |
Co-authored-by: c-bata <[email protected]>
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.
Thanks for the PR. I have several comments. PTAL.
@nabenabe0928 Could you review this PR? |
Sure! |
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.
As a follow-up, it would be great to save the configuration of the setting page in the some storage to maintain the configuration over the page reload, etc.
Sorry for the late response, but now I am working on 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.
Thank you for the PR!
I am still working on the review, but the first yet most important point is that GraphRank.tsx
is missing the color scale setting (yes, I know that rank plot was added recently), so could you apply the same modification to it as well?
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.
Still work in progress, but checked App.tsx and AppDrawer.tsx.
selected={page === "settings"} | ||
> | ||
<ListItemIcon sx={styleListItemIcon}> | ||
<SettingsIcon /> |
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 it better with ColorLens?
Optionally, I would like to discuss if "settings" is an appropriate name for this feature because the name is too general.
If we add any further configurations here in the future, I am definitely for it:)
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.
I left some review comments. Could you check them?
<ListItem key="Settings" disablePadding sx={styleListItem}> | ||
<ListItemButton | ||
component={Link} | ||
to={`${URL_PREFIX}/studies/${studyId}/settings`} |
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 settings seem to be shared among every study. In that case, the url should be${URL_PREFIX}/settings
?
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.
I understand the situation, and you want to remember study_id by url, and go back to previous study page.
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.
How about using pop-up to show setting page? I roughly created my example here, although it is very early implementation and needs improvement.
Some reasons:
- You can use ${URL_PREFIX}/settings instead of "${URL_PREFIX}/studies/${studyId}/settings" here.
- You can show change during tweaking theme on settings.
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, the place of setting should be below because it is for setting for all pages, imo.
You can see this example here
<MenuItem value={"default"}>Default</MenuItem> | ||
<MenuItem value={"seaborn"}>Seaborn</MenuItem> | ||
<MenuItem value={"presentation"}>Presentation</MenuItem> | ||
<MenuItem value={"ggplot2"}>GGPlot2</MenuItem> |
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.
Those templates seem to be for Light mode. Should we only provide templates compatible for dark mode?
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.
Unfortunately, there is only one dark template provided in Plotly's GitHub repository. To offer multiple dark mode templates, we should create original color templates. Therefore, adding (or modifying) an additional dark template could be a suitable follow-up.
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.
@gen740 @c-bata @nabenabe0928 |
I've realized there is a bug that needs to be fixed. Could we please wait to merge this until it's resolved? |
@keisuke-umezawa |
@keisuke-umezawa I've dismissed reviews from both me and @nabenabe0928 since we've been unassigned from this PR. Please merge this PR after checking the latest changes |
@gen740 |
@keisuke-umezawa |
Contributor License Agreement
This repository (
optuna-dashboard
) and Goptuna share common code.This pull request may therefore be ported to Goptuna.
Make sure that you understand the consequences concerning licenses and check the box below if you accept the term before creating this pull request.
Reference Issues/PRs
Fixes #426.
What does this implement/fix? Explain your changes.