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
Personally I am used to and I see .create() more fit in the context of unit testing. What was the reason for this change?
I'm asking because I've been bit by instances where I'm only changing the test (and not the contract) and I was getting wrong results because of initial funding and/or previous state/boxes in the previous deployment.
The text was updated successfully, but these errors were encountered:
@robdmoore this will be addressed as part of updating the template to use new algokit utils with latest interfaces, given that the signature for deploy/create will change. Will tag the issue in PR once utils py interfaces are out and template is ready for update
I've noticed the switch from
.create()
toPersonally I am used to and I see
.create()
more fit in the context of unit testing. What was the reason for this change?I'm asking because I've been bit by instances where I'm only changing the test (and not the contract) and I was getting wrong results because of initial funding and/or previous state/boxes in the previous deployment.
The text was updated successfully, but these errors were encountered: