fix: switch cron-parser to named import (CronExpressionParser)#1737
Merged
Conversation
The default export from cron-parser is deprecated/removed in newer versions. Replace `cronParser` with `CronExpressionParser` in both the cron helper and settings page.
Contributor
|
Odd that it was working before dependencies were updated in commit 9494c34. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The previous Cron Parser was not correctly parsing the cron schedules as shown in the below screenshot
The cron.ts nextCronDate always threw a TypeError which caught and threw Invalid cron
With the fix, it's now showing the correct cron schedules