Update unit testing for compatibility with worker #550
Conversation
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
cgillum
approved these changes
Jun 4, 2025
greenie-msft
pushed a commit
to greenie-msft/azure-functions-durable-python
that referenced
this pull request
Sep 25, 2025
* Update unit testing for compatibility with worker
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Unfortunately, this very cool Callable syntax I had in the original unit testing PR is not compatible with the Python worker, as it uses typing.get_type_hints on whatever value t has for the user function, and get_type_hints does not work on class instances, even if those instances are Callables.
Reverting to the more primative approach, where we simply add the original user functions as properties on the wrapped methods, instead of a dedicated and documented class for now.