Follow-up from "Enable end date/time for rotations"
The following discussion from !50327 (merged) should be addressed:
After checking this I am afraid you're correct, we would need to align the datepicker in the same way we handled the select, I will open a issue for this in the UI lib!
I have tested this myself and can confirm everything works well, the only issue I can see is that we will need to add validation that the end date cannot come before the start date, but I have already added that check in a different branch
😄
Seeing this all in context, I have a couple additional changes. We can make them here or as part of a separate MR, up to you!
In addition to the different color borders on the data picker and the dropdown, the border color of the larger "ends on" box is different than the border color of the name and participants fields.
All the borders should be the same color. Since I'm guessing the participants field is a component, perhaps we should match that one, and have the ends on box border be the same (darker) grey color?
We also appear to have a padding issue when longer timezones are added.
It seems like this could be addressed by shortening the datepicker field a bit - it seems a bit longer than it needs to be. But, we should probably also have a contingency plan in place for longer text values in that timezone space, as we'll want there to be some padding between the end of the text and the edge of the container. I suppose we could wrap text after some point OR have the container grow a bit if needed?