Resume Analyzer Explainability#210
Open
Aditya8369 wants to merge 3 commits 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
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.
Resume analysis now returns structured skill explanations alongside the existing matchedSkills and missingSkills fields, and the model can persist them in ResumeAnalysis.model.js. The controller now builds per-skill evidence from the resume text and required skill source, so each skill gets a status, matchedType, matchedBecause notes, and source context in resumeAnalyzer.controller.js. On the UI, AnalysisResults.jsx now shows expandable rows for each skill with the explanation behind the match or miss.
Validation passed:
get_errorswas clean for the edited files, and a direct Node module-load check for the analyzer backend succeeded. The only output was the existing mongoose duplicate-index warning from other models, which is unrelated to this feature.closes #203