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

Fix trainee dashboard #381

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Fix trainee dashboard #381

wants to merge 1 commit into from

Conversation

kanu-cast
Copy link
Contributor

@kanu-cast kanu-cast commented Oct 24, 2024

PR Description

extending rating schema to include createdAt and updatedAt attributes

Description of tasks that were expected to be completed

simply added createdAt and updatedAt on the Rating schema

@codecov-commenter
Copy link

codecov-commenter commented Oct 31, 2024

Codecov Report

Attention: Patch coverage is 3.03030% with 128 lines in your changes missing coverage. Please review.

Please upload report for BASE (develop@bf4f3cd). Learn more about missing BASE report.

Files with missing lines Patch % Lines
src/resolvers/attendance.resolvers.ts 3.36% 115 Missing ⚠️
src/resolvers/userResolver.ts 0.00% 13 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #381   +/-   ##
==========================================
  Coverage           ?   16.57%           
==========================================
  Files              ?       89           
  Lines              ?     3560           
  Branches           ?     1008           
==========================================
  Hits               ?      590           
  Misses             ?     2961           
  Partials           ?        9           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@ceelogre ceelogre left a comment

Choose a reason for hiding this comment

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

Speak to Shema about my first comment.

src/schema/index.ts Outdated Show resolved Hide resolved
Comment on lines 658 to 676
type traineeAttendanceWeek {
week: Int!
weekAverage: String!
daysStatus: AttendanceDates!
}

type traineeAttendancePhase {
phase: Phase!
phaseAverage: String!
weeks: [traineeAttendanceWeek]!
}

type traineeAttendance {
traineeId: String!
teamName: String!
allPhasesAverage: String!
phases: [traineeAttendancePhase]!
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it necessary to break these into separate types?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think this should go to the team that has been working on attendance as i never altered any of these types and i think if i do alter or combine these types it might affect their work. Thanks

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.

5 participants