-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix:tests #28
fix:tests #28
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving with minor suggestions
PackedUserOperation[] memory ops = new PackedUserOperation[](1); | ||
(PackedUserOperation memory userOp, bytes32 userOpHash) = createUserOp(ALICE, bicoPaymaster, priceMarkup); | ||
(PackedUserOperation memory userOp, bytes32 userOpHash) = createUserOp(ALICE, bicoPaymaster, 1_100_000, 100_000); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above, name params for more readability
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was avoiding local vars :/
Co-authored-by: filmakarov <[email protected]>
Co-authored-by: filmakarov <[email protected]>
Co-authored-by: filmakarov <[email protected]>
revamp (WIP) test cases and helpers a bit to avoid running into stack too deep issues.
for further work on this repo,
keep these in mind
i. Bundling related parameters into struct - those are used repeatedly.
ii. Minimize number of local variables and identify areas where it can be block scoped.
iii. Offload intermediate variables into memory to avoid direct stack operations
iv. Review order of variable initialisation
v. can work on further breaking down complex functions.
Note that paymaster validation gas limit, callGasLimit, verificationGasLimit estimations are currently skipped. either ways they can not be accurate without using gas estimation package.
unaccountedGasCost should be kept appropriate value after testing, when there is premium to be charge unaccountedGas needs to be higher value (also depending on warm/cold slot of fee collector)