Referral Status Timeline#208
Open
Aditya8369 wants to merge 1 commit into
Open
Conversation
|
@Aditya8369 is attempting to deploy a commit to the omkarhole's projects Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implemented the referral status timeline end to end. The backend now stores an append-only timeline on each referral document, appends events when a referral is posted, applied to, accepted, rejected, or closed, and exposes
GET /api/referrals/:id/timelineplus a poster/admin close action. The role checks are now enforced in the actual flow: students can apply, and only the poster or an admin can accept/reject/close. See JobReferral.model.js, referral.controller.js, and referral.routes.js.On the UI side, ReferralDetail.jsx now fetches the timeline endpoint and renders a chronological activity feed with timestamps, status labels, and optional actor/applicant names. I also fixed the detail page to use the session ID stored in localStorage instead of a missing
userobject from auth context, so ownership and apply gating work with the existing auth setup. The edited files passedget_errors, and a direct Node module-load sanity check succeeded.closes #201