You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @syberen, thanks for the catch. start_from_beginning should be bool, and start_from_time should be str. I've linked a PR with these changes. However, since we're currently in a release freeze with the holidays and this is a minor fix, release ETA is January.
The properties are mentioned in the documentation linked, but they're under the Configuration section. I agree though that the wording for the Decorators and Configuration sections is misleading. I'll work to get that updated, so that the V1 and V2 properties are accurately displayed.
Expected Behavior
When using the
start_from_time
andstart_from_beginning
parameters, no typing errors should occur.Actual Behavior
These fields (
start_from_time
andstart_from_beginning
) are both typed asOptional[time]
. It seems to me like it should be:Also, the fields are not correctly documented in microsoft learn:
https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-cosmosdb-v2-trigger?tabs=python-v2%2Cisolated-process%2Cextensionv4%2Cnodejs-v4&pivots=programming-language-python#example
Steps to Reproduce
Go to this link and you will see the incorrect types
Relevant code being tried
Relevant log output
requirements.txt file
Where are you facing this problem?
Local - Core Tools
Function app name
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: