fix(ui): advise users on correct chron syntax for scheduling #12854
+91
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We recently added backend support for more advanced cron syntax. For example, to schedule ingestion on the 2nd Monday of every month you could do either "0 0 0 0 1#2" or "0 0 8-14 0 1". However, only the 2nd method is supported on the frontend. For example, when using the hashmark syntax, if you switch in and out of the advanced tab it will get erased:






But when using the other syntax, everything works:
Long story short: this is because the frontend uses two different libraries for cron: one that supports # and one that doesn't. I think these code changes are an acceptable alternative but I'm open to other ideas. The test I added is just for the backend to make sure both ways work.

With my changes, the user will not able to uncheck the advanced box if they use the hashmark. This is what you see when you put a hashmark in the schedule:
Checklist