CODE RUB: Corrected Validation exception for Modify

[rcruzfreelance]

Closes #571

[ShriHumrudha]

I am thinking out loud if we want to keep the data arranging explicit in the test for the storytelling.

[hassanhabib]

I am thinking out loud if we want to keep the data arranging explicit in the test for the storytelling.

@ShriHumrudha we can also expose an input parameter for dates - either way is okay.

[mtoncic]

I am thinking out loud if we want to keep the data arranging explicit in the test for the storytelling.

@ShriHumrudha we can also expose an input parameter for dates - either way is okay.

Fill like free to jump since I created an issue.
In the proposed solution there is a version:

  DateTimeOffset createdAndUpdatedDate = DateTimeOffset.UtcNow;
  Student randomStudent= CreateRandomStudent(dates: createdAndUpdatedDate);
  Student invalidStudent = randomStudent;

I think that this would be the right match.

[hassanhabib]

I am thinking out loud if we want to keep the data arranging explicit in the test for the storytelling.

@ShriHumrudha we can also expose an input parameter for dates - either way is okay.

Fill like free to jump since I created an issue. In the proposed solution there is a version:

  DateTimeOffset createdAndUpdatedDate = DateTimeOffset.UtcNow;
  Student randomStudent= CreateRandomStudent(dates: createdAndUpdatedDate);
  Student invalidStudent = randomStudent;

I think that this would be the right match.

@mtoncic that's a bad version. The dates here are generated from the datetime instead of random. We should randomize instead. The reason for the randomization here is to ensure that nobody is adding some crazy rule that says only throw exception if dates are the same AND recent. We don't want to do that for any reason.

[hassanhabib]

Closing this due to inactivity