Generalize logic to get trigger options #130
Merged
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.
I always hated manually specifying these trigger properties, but I never had a cleaner way to do it and keep TypeScript happy (without resorting to
any
types everywhere). Well, I think I figured one out. Here's the basic idea:I had to work some magic to combine it into one shared function, but got it figured out for everything except the cosmos one. Something about the union type
CosmosDBv3TriggerOptions | CosmosDBv4TriggerOptions
is throwing TypeScript off, but functionally it should be fine and I still prefer this overall.