OWASP / OWASP/Nest

Implement Robust Module Date Validation When Program Dates Change

Open
#4,045 13 comments 0 reactions 0 assignees View on GitHub
backend frontend
Dominant language
Python
Stars
451
Forks
702
Avg merge
22h 59m
Merged PRs (30d)
91

Description

When an administrator updates the overall date range for a mentorship program, any associated module dates may end up outside this new window—causing inconsistent or invalid data. It's important to ensure all module dates remain within the program's start and end dates after such changes.

**Proposed Solution:** Automatically adjust module dates to stay within the new program range:

- If a module's start date is before the program's new start, reset the module's start to match the program start.
- If a module's end date exceeds the program's new end, reset the module's end to match the program end.

This approach prioritizes consistent data integrity with minimal manual intervention.

**Advantages:**

- Keeps module timelines valid without requiring extra admin steps
- Reduces the chance of orphaned or misaligned modules

**Potential Drawback:**

Module dates may be changed silently, potentially confusing users. Consider providing a clear notification when automatic adjustments occur.

**Discussion:** Feedback is welcome on this approach or alternative strategies to ensure module and program dates always remain consistent and clear to users.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.