Let cron depend on interface for parsers instead of fixed parser #243
Conversation
This file contains 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
|
@robfig I'm hoping you will consider this PR. If anything needs to be changed for this to get accepted, please let me know. |
|
It is a non invasive change that will allow us and others to implement our own custom parsers. Thanks @robfig |
|
Seems reasonable. Thanks! |
haiheipijuan
pushed a commit
to haiheipijuan/cron
that referenced
this pull request
Jun 15, 2021
Let cron depend on interface for parsers instead of fixed parser
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change allows cron to use another or extended parser instead of the one that comes in the package.