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
Function arguments are first resolved by type, then by name. After your modification, both a and b have int type, so type resolution (resolve by int and int) takes precedence over name resolution (resolve by a and b), which leads to incorrect values being injected during a function call. For sure this logic could be more sophisticated, but at this point I have no plans for working on it, but please feel free to contribute :)
As a workaround, you can implement your own DependencyProvider that implements your own resolve_func_params and instantiate an app or transaction context with it using
Thanks @pgoreck for prompt and clear answeri ! Need to think how I want to approach this :) Kindly please let's keep this issue open for a little bit while. Thanks!
lato/tests/test_transaction_context.py
Line 8 in 18c2afa
after modifying
tests/test_transaction_context.py
from
to
test suite fails:
P.S. Thanks a lot for creating and open source'ing python-ddd repo ant lato! Welki dzeki! :)
The text was updated successfully, but these errors were encountered: