Skip to content

fix: handle spaced date ranges and prevent overwriting existing endDates in parse_date_range #389

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.

Sign up for GitHub

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

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

fix: handle spaced date ranges and prevent overwriting existing endDates in parse_date_range #389

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions transform.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,6 +200,8 @@ def transform_work_experience(work_list: List) -> List[Dict]:
]
):
start_date, end_date = parse_date_range(start_date_input)
if not end_date:
end_date = item.get("endDate")
else:
# Use existing startDate and endDate values
start_date = item.get("startDate")
Expand Down Expand Up @@ -425,6 +427,12 @@ def parse_date_range(date_range: str) -> tuple:
return start_part, "Present"
return None, "Present"

# Handle standard range with space-hyphen-space
if " - " in date_range:
parts = date_range.split(" - ")
if len(parts) == 2:
return parts[0], parts[1]

# Handle format like "Jan-Mar 2021"
if " " in date_range and any(
month in date_range
Expand Down