client: imports: avoid error when cron string cannot be parsed when trying to edit imports To prefill the form fields that generate the cron string, the currently stored cron string needs to be parsed back. This parsing only handles numerical values for each of the six cron fields. In case of something like */15 the regular expression does not match, leading to a null value. The cronMode select now has an empty option for cases where the cronString does not match any known pattern.

532c8392048fe720bf31b7efb475591ab95a74ec v1-uat1
136aaa7f00af0b500c5c75f9fd9aabfc7fa526ee v1.1.0
724758455a4e44d25b096f00bcb353ceda0e0d57 v2-preview20190111
0059aa870a396e2112efae43f822c0c133454d7a v2
83f9a131dfb69f3ea1f430728a0831ccf96316d7 v2.1.0
83f9a131dfb69f3ea1f430728a0831ccf96316d7 v2.1.0
4d69b79e9df6e2b646ac60f75f6655bb3c64f6c6 v2.1.0