Convert the Education section to Optional

[dimitarmanov]

Pull Request Title

Allow processing of resumes without having the Education section

Description

My resume doesn't have an Education section. Due to this, I was receiving an error (will be shown below)
After making the change, even resumes without Education listed can be processed.

Type

• Bug Fix
• Feature Enhancement
• Documentation Update
• Code Refactoring
• Other (please specify):

Proposed Changes

• Convert the Education class to optional instead of required

Screenshots / Code Snippets (if applicable)

Error looks like this:
[dev:backend] [2025-08-18T08:10:16+0300 - app.api.router.v1.resume - WARNING] Resume validation failed: Resume structure validation failed: Resume validation failed. Education -> 0 -> startDate: Input should be a valid string; Education -> 0 -> endDate: Input should be a valid string

How to Test

Testing doesn't change as the originally described.

Checklist

• The code compiles successfully without any errors or warnings
• The changes have been tested and verified
• The documentation has been updated (if applicable)
• The changes follow the project's coding guidelines and best practices
• The commit messages are descriptive and follow the project's guidelines
• All tests (if applicable) pass successfully
• This pull request has been linked to the related issue (if applicable)

Additional Information

Although it is not a crucial "bug", not all resumes include Education for factors like working in a field or applying to a field that is not related to your education.

---

Summary by cubic

Resume validation no longer fails when the Education section is missing. Education is now optional, and date fields within Education are optional too.

• Bug Fixes
  • education in StructuredResumeModel now defaults to an empty list (alias "Education").
  • Education.startDate and Education.endDate changed to Optional[str].
  • Prevents "invalid string" errors when Education is absent or dates are not provided.

Summary by CodeRabbit

• New Features

  • Resumes can be submitted without education start/end dates; these fields are now optional.
  • The Education section is now optional; resumes without it will be accepted and treated as an empty list.

• Bug Fixes

  • Prevents validation errors when education dates are missing.
  • Eliminates failures when the Education section is absent in uploaded resumes.

[coderabbitai]

Walkthrough

The Pydantic schema for structured resumes was updated: Education.start_date and Education.end_date are now optional, and StructuredResumeModel.education is now an optional list with a default empty list via default_factory.

Changes

Cohort / File(s)	Summary
Pydantic schema adjustments apps/backend/app/schemas/pydantic/structured_resume.py	Made Education.start_date and end_date Optional[str] with aliases unchanged; changed StructuredResumeModel.education from required to a list with default_factory=list (alias "Education").

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my whiskers at fields now free,
Dates may wander, or choose not to be.
An empty school list? I won’t complain—
I’ll default a basket, neat and plain.
Hop, hop—schemas softened with glee!

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Backward Compatibility Making education default to an empty list changes validation behavior; ensure downstream consumers don't rely on presence of Education being required or on non-empty lists to trigger logic. education: List[Education] = Field(default_factory=list, alias="Education") extracted_keywords: List[str] = Field( Data Semantics start_date and end_date are now optional strings; consider whether date parsing/ordering logic elsewhere handles None and empty strings safely, and if stricter types (e.g., date format validators) are needed. start_date: Optional[str] = Field(None, alias="startDate") end_date: Optional[str] = Field(None, alias="endDate")

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Enforce paired optional dates Keep these fields optional, but enforce that if one date is provided, the other must be provided too to avoid partial ranges. Add a Pydantic model-level validator to ensure start_date and end_date appear together or both be null. apps/backend/app/schemas/pydantic/structured_resume.py [58-59] start_date: Optional[str] = Field(None, alias="startDate") end_date: Optional[str] = Field(None, alias="endDate") +@classmethod +def model_validate(cls, value): + model = super().model_validate(value) + if (model.start_date and not model.end_date) or (model.end_date and not model.start_date): + raise ValueError("Both 'start_date' and 'end_date' must be provided together or both omitted.") + return model + Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies a potential data integrity issue where one date in a range might be provided without the other, and proposing a validator is a valid improvement.	Low
	Preserve absence vs. empty distinction Distinguish between missing and explicitly empty education by making the field Optional with a default of None. This prevents silently converting absent data into an empty list, which can affect downstream logic that checks for presence. apps/backend/app/schemas/pydantic/structured_resume.py [73] -education: List[Education] = Field(default_factory=list, alias="Education") +education: Optional[List[Education]] = Field(default=None, alias="Education") Apply / Chat Suggestion importance[1-10]: 5 __ Why: The suggestion offers a valid alternative for handling the absence of the education field, which could be beneficial depending on the desired behavior of downstream logic.	Low
More

[cubic-dev-ai]

cubic analysis

No issues found across 1 file. Review in cubic

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

apps/backend/app/schemas/pydantic/structured_resume.py (1)

73-73: No Education: null occurrences found in fixtures
The default_factory=list already ensures that missing "Education" deserializes to []. I ran a search through our sample payloads and didn’t find any instances of "Education": null. That said, absence of evidence isn’t proof—if upstream systems might send null, you can still opt in to coercing it:

# Add at the top of apps/backend/app/schemas/pydantic/structured_resume.py
from pydantic import field_validator

# Inside StructuredResumeModel (below the field definitions)
@field_validator("education", mode="before")
@classmethod
def _coerce_null_education(cls, v):
    return [] if v is None else v

No action is strictly required unless you’ve seen null payloads in production.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 8c75adf and 2514c2e.

📒 Files selected for processing (1)

• apps/backend/app/schemas/pydantic/structured_resume.py (2 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

apps/backend/app/schemas/**/*.py

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

Use Pydantic models for request/response schemas and validation

Files:

• apps/backend/app/schemas/pydantic/structured_resume.py

🧬 Code Graph Analysis (1)

apps/backend/app/schemas/pydantic/structured_resume.py (2)

apps/backend/app/schemas/pydantic/resume_preview.py (2)

• EducationItem (25-30)
• ResumePreviewerModel (33-38)

apps/backend/app/schemas/pydantic/structured_job.py (2)

• Qualifications (79-81)
• StructuredJobModel (95-112)

🔇 Additional comments (1)

apps/backend/app/schemas/pydantic/structured_resume.py (1)

58-59: No downstream string-only usage of start_date/end_date detected

I searched the entire codebase for any .start_date or .end_date references (including chained string methods) and found none. It’s safe to make these fields optional as there are no consumers assuming they’re always non-null strings.