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 cm edit goal #272

Merged
merged 37 commits into from
Mar 7, 2024
Merged

Feat cm edit goal #272

merged 37 commits into from
Mar 7, 2024

Conversation

KCCPMG
Copy link
Contributor

@KCCPMG KCCPMG commented Dec 1, 2023

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)

…ming form, change Goal mapping in Iep component to List and ListItem from ul and List
…ror handler on [goal_id] for editGoal mutation
…parent stack to 1200px to match MUI containers
Copy link
Contributor

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

src/backend/routers/iep.ts Show resolved Hide resolved
src/backend/routers/iep.test.ts Outdated Show resolved Hide resolved
src/components/goal/Goal.tsx Outdated Show resolved Hide resolved
src/components/goal/Goal.tsx Outdated Show resolved Hide resolved
src/components/goal/Goal.tsx Outdated Show resolved Hide resolved
src/components/goal/Goal.tsx Outdated Show resolved Hide resolved
src/pages/goals/[goal_id].tsx Outdated Show resolved Hide resolved
src/styles/GoalPage.module.css Outdated Show resolved Hide resolved
Copy link
Contributor

@codetheweb codetheweb left a 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?

@KCCPMG
Copy link
Contributor Author

KCCPMG commented Dec 12, 2023

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?

@tessathornberry
Copy link
Contributor

tessathornberry commented Dec 12, 2023

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:

  1. create a differently-named new local branch for that particular task (something like feat-goal-page, feat-goal-edit, feat-goal-edit-tests, feat-goal-css, or what you think is right)
  2. commit code for just one task
  3. push code up to that distinct branch and make a PR for that task
  4. start at 1 above except with the new branch based on the code from your just-submitted PR

You can leave this PR as-is, I think! ;)
If you want to add your broken-out tasks as simple issues you refer to with each smaller PR, you can do that here and then add those by editing the main issue as tasks with checkboxes like [ ] - #taskIssueNumber

@KCCPMG KCCPMG mentioned this pull request Feb 8, 2024
@KCCPMG KCCPMG linked an issue Feb 15, 2024 that may be closed by this pull request
2 tasks
@@ -0,0 +1,53 @@
.goalDescriptionContainer {
background-color: #ffffff;
Copy link
Contributor

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

Copy link
Contributor Author

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.

Copy link
Contributor

@tessathornberrypadg tessathornberrypadg left a 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

@KCCPMG KCCPMG merged commit 6a388a0 into main Mar 7, 2024
3 checks passed
@hieungo89 hieungo89 deleted the feat-cm-edit-goal branch March 7, 2024 23:20
@KCCPMG KCCPMG mentioned this pull request Mar 8, 2024
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.

Make Editing Goals possible [ENG]
5 participants