[Contracts] Validate Notification Expiration Windows

[Abd-Standard]

Description

Prevent registration of notifications with invalid expiration timestamps.

Acceptance Criteria
Expired timestamps are rejected.
Unit tests cover boundary conditions.
Validation errors are descriptive.

[fathiaoyinloye]

Hi maintainers,

I'd like to work on this issue.

I have experience building backend validation logic, API safety checks, and writing unit tests for edge cases. After reviewing the requirements, I understand that the goal is to enforce strict validation for notification expiration timestamps to prevent invalid or expired data from being registered.

My approach would be to:

• Add validation logic to reject notifications with expired or invalid timestamp values.

• Ensure validation runs consistently at the service or DTO layer (depending on existing architecture).

• Provide clear, descriptive validation error messages to help developers and consumers understand why a request failed.

• Add unit tests covering boundary conditions such as:

  • timestamps in the past
  • current time edge cases
  • extremely large or malformed values

• Ensure all existing notification flows remain unaffected by the new validation rules.

I will make sure the implementation is robust, well-tested, and aligned with the project's existing validation patterns.

Please assign this issue to me if it is available. Thank you!

[ayomidearegbeshola29-dev]

As a Full-Stack Developer, I would address this issue by implementing server-side validation to ensure notifications cannot be registered with expiration timestamps that are already in the past.

The validation logic would be added at the API and service layers to verify that the provided expiration timestamp is greater than the current system time before a notification is created or stored. If an invalid timestamp is detected, the request will be rejected with a clear and descriptive validation error explaining that the expiration date must be in the future.

To maintain consistency, I would leverage existing validation mechanisms (DTO validation, custom validators, or service-level checks) and ensure that invalid data cannot bypass validation through direct service calls.

I would also add comprehensive unit tests covering key boundary conditions, including:

• Expiration timestamp in the past.
• Expiration timestamp equal to the current time.
• Expiration timestamp slightly in the future.
• Valid future timestamps.

These tests will verify that expired timestamps are consistently rejected while valid future timestamps are accepted.

Skills Applied: TypeScript, Full-Stack Development, Backend Validation, API Development, Error Handling, Unit Testing, Edge Case Analysis, Code Quality, and Maintainable Software Design.

[dolaoluwa574-source]

I’m excited to contribute to impactful software improvements. My experience includes backend engineering, object-oriented programming, API development, Git collaboration, and building scalable, maintainable applications.

[michaelvic123]

I’d love to work on this issue. I’m a full-stack developer with experience building and maintaining web applications across both frontend and backend technologies. The issue looks interesting, and I’m confident I can contribute a solid solution.

[grantfox-oss]

🦊 GrantFox — @michaelvic123 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #96)
2. Your PR will be reviewed by the Core-Foundry maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@michaelvic123's PR #112 was approved and merged by @Abd-Standard.

🏆 @michaelvic123: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (583 total points). Track your full progress on GrantFox.

👏 Great work, @michaelvic123! Keep contributing to Core-Foundry.