Not sure if I like that this is the case, or at least I ran into an issue where I expected that putting a timedelta object in the deployment params of a contract that expected a timedelta arg ended up making a quite large timedelta unexpectedly
Should this converter instead convert timedelta as td.total_seconds(), and then suggest in the docs to do datetime + timedelta for those scenarios where you want it to produce a specific timestamp and not a delta? e.g.
Not sure if I like that this is the case, or at least I ran into an issue where I expected that putting a
timedelta
object in the deployment params of a contract that expected a timedelta arg ended up making a quite large timedelta unexpectedlyhttps://github.com/ApeWorX/ape/blob/13ea95253a75d9576d5f89f6378254abda200e9e/src/ape/managers/converters.py#L229
Should this converter instead convert
timedelta
astd.total_seconds()
, and then suggest in the docs to dodatetime + timedelta
for those scenarios where you want it to produce a specific timestamp and not a delta? e.g.