DatePicker improvements

[danielskovli]

Description

As a user of a form that has a start and end date, I would like the end date to default to the view of the start, so I can more easily pick dates far in the future.

Additional Information

Linking two or more DatePicker components would make the user experience when picking related dates smoother. For instance, if picking a start date a year in the future, you have to click a handful of times to get that far. Then you move on to the end date component, which defaults to today's date and you have to perform the exact same clickathon again.

Not only is this cumbersome, it increases the risk of incorrect data being entered by the user.

Acceptance Criterias

• Defaulting a DatePicker's view to the value of another DatePicker's selected value should be possible. Note that the DatePicker value itself should not be automatically set to anything, just that the selection view should be navigated to the right day/month/year/milliennia

[olemartinorg]

You can probably already do this, in a way, with a backend data processor. That is, set the end-date when you select the start date (and potentially add a validation for if both dates are the same, which you would then want to show up later if the user tries to submit that data). Not optimal, but adding this as a suggested workaround for now.

[danielskovli]

What if the end-date already contains a value? Then I select a new start-date sometime further in the future than the current end-date. I don't think it would be correct behavior for the data processor to overwrite the existing end-date at this point, but it would be nice if the picker understands the start-date context when I click it next.

Does that make sense?

I'm not the authority on this, of course, just happens to be the guy who supplied an issue based on something the apps migration team was building 😄

[olemartinorg]

Hmm, I think validation would be the answer to that as well. An end date cannot be before a start date, so that should have a validation. But yep, overall I think we would have to map out our alternatives here and find a solution that would works properly - and that we'd want to support in our apps. Something that looks more like the two-date duration-pickers you see when booking flights tickets, for example.