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

Benchmark creation #298

Merged
merged 9 commits into from
May 14, 2024
Merged

Benchmark creation #298

merged 9 commits into from
May 14, 2024

Conversation

codetheweb
Copy link
Contributor

@codetheweb codetheweb commented Mar 3, 2024

Screen.Recording.2024-03-03.at.8.27.03.PM.mov

Future improvements:

  • fix breadcrumbs
  • finish benchmark listing page (/goals/[goal_id])
  • input validation
  • re-use same form for editing benchmarks

@codetheweb codetheweb force-pushed the feat-create-benchmark branch from c8d3907 to b3fe5cb Compare March 4, 2024 04:30
@codetheweb codetheweb linked an issue Mar 4, 2024 that may be closed by this pull request
@codetheweb codetheweb marked this pull request as ready for review March 4, 2024 04:33
@codetheweb codetheweb requested review from tessathornberry and KCCPMG and removed request for tessathornberry March 4, 2024 04:33
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.

This looks great, @codetheweb. Other than maybe cleaning up any minor "this variable was defined but never used" github messages which are noted in your changed files here, this is good as is for this step. Nice work!
OF COURSE, me writing that includes that I agree with the "future fixes" you mentioned in the notes on your PR. :D

@@ -51,7 +52,7 @@ const Goals = ({ goal }: GoalProps) => {
gap: "8px",
}}
>
<button
<Link
// standin for tertiary button style
style={{
display: "inline-flex",
Copy link
Contributor

Choose a reason for hiding this comment

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

☀️ We may add to a future ticket to move all this CSS into the sibling CSS file rather than having it in the components, but that goes for the whole app. Plus behavior may vary when combined with MUI components, so we can put that off a bit longer.

src/components/goal/Goal.tsx Show resolved Hide resolved
<div>
{goal && (
<GoalHeader
name="[placeholder] 1st Goal"
Copy link
Contributor

Choose a reason for hiding this comment

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

☀️ Future functions may track which goal and change wording to "Goal 1" etc.

const handleSubmit = async (e: React.FormEvent<HTMLFormElement>) => {
e.preventDefault();
const form = e.currentTarget as HTMLFormElement;
const formData = new FormData(form);
Copy link
Contributor

Choose a reason for hiding this comment

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

☀️ This is cool

</Stack>
</Stack>

<Divider />
Copy link
Contributor

Choose a reason for hiding this comment

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

☀️ ok, these are cool

Copy link
Contributor

@KCCPMG KCCPMG left a comment

Choose a reason for hiding this comment

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

Mild conflict with the [goal_id] page in PR #272 which was just merged. Quick summary of those differences from the perspective of what was just merged:

  • Clicking on a goal goes to goals/[goal_id] instead of students/[student_id]/goals/[goal_id]. What you have here seems much better to me, especially considering that breadcrumbs are now working.
  • The [goal_id] page recently merged in was largely following this design, which contains the goal editing functionality. Nothing in the benchmark section has been implemented yet aside from the selectable tabs, but according to that original design this is where that add benchmark button should go.

@KCCPMG KCCPMG requested review from hieungo89 and removed request for hieungo89 April 23, 2024 01:48
KCCPMG added 4 commits April 22, 2024 21:18
@KCCPMG KCCPMG requested review from KCCPMG, hieungo89 and tessathornberry and removed request for KCCPMG April 25, 2024 01:26
@tessathornberry tessathornberry requested a review from katconnors May 9, 2024 02:56
@tessathornberry tessathornberry mentioned this pull request May 9, 2024
@katconnors
Copy link
Contributor

katconnors commented May 10, 2024

There's a bit of a bug on github's end where I can only view the file changes for the 7 total commits (the 3 original ones, plus the 4 recent ones). Alternatively, is it possible to submit the PR to only include the changes that are within the scope of the issue? (I believe there are 9 commits for other PR's, since this PR references 16 commits)

@KCCPMG
Copy link
Contributor

KCCPMG commented May 10, 2024

There's a bit of a bug on github's end where I can only view the file changes for the 7 total commits (the 3 original ones, plus the 4 recent ones). Alternatively, is it possible to submit the PR to only include the changes that are within the scope of the issue? (I believe there are 9 commits for other PR's, since this PR references 16 commits)

I'm not quite sure I understand....it sounds like you can see Max's original 3 commits, can't see the commits from merging main back into this branch to re-sync, and then you can see the 4 commits that I made since then?

@katconnors
Copy link
Contributor

On the functionality side, I haven't been able to add a benchmark.
On my first attempt, I filled in all fields except for "metric to track", and I received this error:
image
I've since been unable to replicate the error, but the benchmarks don't appear when I submit the form (even with all fields completed).

@katconnors
Copy link
Contributor

There's a bit of a bug on github's end where I can only view the file changes for the 7 total commits (the 3 original ones, plus the 4 recent ones). Alternatively, is it possible to submit the PR to only include the changes that are within the scope of the issue? (I believe there are 9 commits for other PR's, since this PR references 16 commits)

I'm not quite sure I understand....it sounds like you can see Max's original 3 commits, can't see the commits from merging main back into this branch to re-sync, and then you can see the 4 commits that I made since then?

For my review, I wanted to isolate the file changes to just the 4 commits you've made, because Max's commits already had reviews. I would assume it's a bug, because I can do a number of other combinations within the selections.

@KCCPMG
Copy link
Contributor

KCCPMG commented May 10, 2024

On the functionality side, I haven't been able to add a benchmark. On my first attempt, I filled in all fields except for "metric to track", and I received this error: image I've since been unable to replicate the error, but the benchmarks don't appear when I submit the form (even with all fields completed).

You may need to re-run the migrations file. I believe that Max's earlier commits included an alternation of the schema in initial migrations.

@katconnors
Copy link
Contributor

I re-ran the migrations file and the feature worked for me. I took a look at the three latest commits, and don't have any suggestions.

@KCCPMG KCCPMG removed their request for review May 13, 2024 22:08
@KCCPMG KCCPMG merged commit 798e040 into main May 14, 2024
3 checks passed
@KCCPMG KCCPMG deleted the feat-create-benchmark branch May 14, 2024 00:05
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.

Benchmark creation page
4 participants