-
Notifications
You must be signed in to change notification settings - Fork 14
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 cm edit goal #272
Feat cm edit goal #272
Conversation
…ss to include type
…le, re-run type-css
…component within Goal component
…ming form, change Goal mapping in Iep component to List and ListItem from ul and List
…n.default, button.secondary
…oal_id] and .mainGoal to Layout component
…ror handler on [goal_id] for editGoal mutation
…parent stack to 1200px to match MUI containers
… to match main, tests passing
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.
Please look over all of the whiteboxed system-created comments as well you can see them on the changes 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.
the size of this makes it a bit difficult to review, would it be possible to split this up into a few separate PRs? maybe one for the design updates and one for the goal edit page?
Honestly I'm not sure how I would go about doing that at this point. Is there an easy way to do that, especially one that would preserve the comments that Tessa already made? |
If it were me, I might start from the current main branch and for each of the tasks, follow the sequence of:
You can leave this PR as-is, I think! ;) |
…liminate bacgkround color change on hover on rendered goals
src/styles/GoalPage.module.css
Outdated
@@ -0,0 +1,53 @@ | |||
.goalDescriptionContainer { | |||
background-color: #ffffff; |
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 can use the global-defined variable for colors instead of the color palette. All the global variables are defined in globals.css
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.
Got it. There was one color I kept as is since there was no global variable to handle it, but the others I found and utilized.
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 looks good, Connor! Please update the CSS per our discussion
…es in styles/GoalPage.module.css
Update Iep and Goal components to bring them closer to relevant figma designs, create [goal_id] page to enable goal edits, create backend procedure for editing goals on iep router.
Possible issues to create after merge:
-Build Add Benchmark page (also Edit Benchmark page?)
-Standardize/Transfer to CSS styling for Add Benchmark link
-Correct Goal component alignment with design, including toast notifications
-Correct Iep component alignment with design, including toast notifications
-Build out rest of [goal_id] page to align with design (rendering subgoals)