You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our application, we have an 'End Date' field for events, and we have multiple checks for the End Date field across multiple parts of the application. The issue is that the 'End Date' field is never used in our application and it usually getting reassigned to the Start Date value, meaning that it lacks much utility as a field. Unless we envisage the possibility of multi-day events, deleting the End Date field from our database might be the path to take.
An instance of assigning End Date to Start Date during event creation:
Unnecessary check for End Date in Renew Event (Renew Event also does not have an End Date field in its form):
The text was updated successfully, but these errors were encountered:
In our application, we have an 'End Date' field for events, and we have multiple checks for the End Date field across multiple parts of the application. The issue is that the 'End Date' field is never used in our application and it usually getting reassigned to the Start Date value, meaning that it lacks much utility as a field. Unless we envisage the possibility of multi-day events, deleting the End Date field from our database might be the path to take.
An instance of assigning End Date to Start Date during event creation:
Unnecessary check for End Date in Renew Event (Renew Event also does not have an End Date field in its form):
The text was updated successfully, but these errors were encountered: