Can't set a Due Date that has a leading zero in time, errors with `invalid time` about wekan

[juppees]

You may try to omit the leading zero - this works at least for me. With a leading zero, the same error arrises.

[C0rn3j]

You may try to omit the leading zero - this works at least for me. With a leading zero, the same error arrises.

Thanks for that workaround and nailing it down!

09:00 errors but 9:00 works just fine.

[C0rn3j]

wekan/client/lib/datepicker.js

Lines 6 to 11 in f311359

	function adjustedTimeFormat() {
	return moment
	.localeData()
	.longDateFormat('LT')
	.replace(/HH/i, 'H');
	}

wekan/client/lib/datepicker.js

Lines 102 to 120 in f311359

	'submit .edit-date'(evt) {
	evt.preventDefault();
	// if no time was given, init with 12:00
	const time =
	evt.target.time.value ||
	moment(new Date().setHours(12, 0, 0)).format('LT');
	const newTime = moment(time, adjustedTimeFormat(), true);
	const newDate = moment(evt.target.date.value, 'L', true);
	const dateString = `${evt.target.date.value} ${time}`;
	const newCompleteDate = moment(
	dateString,
	`L ${adjustedTimeFormat()}`,
	true,
	);
	if (!newTime.isValid()) {
	this.error.set('invalid-time');
	evt.target.time.focus();
	}

Well it's here, but I am not 100% sure how to fix it.

[C0rn3j]

This makes 9:00 be invalid instead, which is perhaps not ideal, but at least it corresponds to the HH:mm hint.

Side note, is there a way to add the variable that's problematic to the error output?

Invalid time: "9:00", expected HH:mm format would make the issue even more obvious.
I honestly did not understand at first that it was the TIME that was the problem, despite it saying so and even highlighting the form. I though the date could also be wrong somehow.