El De-dog-lo
El De-dog-lo
> @unparalleled-js @fubuloubu @NotPeopling2day is `dev_message` intended to be mutually exclusive with the existing `expected_message`? Yes, mutually exclusive checks > Also Bryant had mentioned allowing regex in the kwargs for...
Not seeing a way for a contract method to pass this parameter ```py >>> foo.bar(False, sender=dev, raise_on_fail=True) ... ContractLogicError: Transaction failed. ```
> > Not seeing a way for a contract method to pass this parameter > > ```python > > >>> foo.bar(False, sender=dev, raise_on_fail=True) > > ... > > > >...
overall, I think this might need some good QA over the different circumstances that raise errors
will have to do a bit of QA on this
> ## Future State > Later on it should have the following behavior: > > ```python > ... > > # Inside ape.reverts(), gas estimation always passes but failed receipts...
> > @unparalleled-js the issue I'm running into is that if we completely bypass gas estimation, the `txn.gas_limit` remains `None` which causes a missing field error later on when signing...
> 1. Have a way to rename account aliases This would be handy, maybe CLI method under `ape accounts`? > 2. Define .ape/plugin directory to specifcy it is for accounts...
> Should we force the query to pull all data from the provider if it doesn't exist? That way we could populate the cache db. If you wanted to only...
> @banteg I am pushing the ContractEvents off to implement this properly with the `DefaultQueryProvider` and I have to add a method upstream. So I am holding off on that...