fix: fix object constructor typings & make OC generic type optional #712
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.
Description
the generic typings on the
CronJob.from()
method were not up-to-date withCronJob
's typings, this PR updates them.while working on this, I attributed a default to the
OC
generic parameter to improve usage convenience (that was previously bugging out the TypeScript compiler type's inference).we might want to consider substituting the generic place since users will need to type
C
more often thanOC
, but that would imply releasing a new major version, so we can probably leave it as is for now since we can doCronJob<CronOnCompleteCommand, { key: 'value' }
to type bothcontext
andonComplete
, orCronJob<null, { key: 'value' }
to omitonComplete
.Related Issue
Discord thread: "How to trigger onComplete?"
Motivation and Context
CronJob.from()
methodOC
generic type parameter could be optionalHow Has This Been Tested?
Types of changes
Checklist:
!
after the type/scope in the title (see the Conventional Commits standard).