getExecutionData() to Also Include Execution Hooks for Native Account Selectors#221
Open
0xrubes wants to merge 2 commits intoerc6900:developfrom
Open
getExecutionData() to Also Include Execution Hooks for Native Account Selectors#2210xrubes wants to merge 2 commits intoerc6900:developfrom
getExecutionData() to Also Include Execution Hooks for Native Account Selectors#2210xrubes wants to merge 2 commits intoerc6900:developfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There's a minor bug in the
getExecutionData()view function. It will currently not return the execution hooks for the ERC-6900-native account selectors, asexecutionData.executionHooksis only populated in the case the selector is not an account selector.Solution is super straight forward, to have
executionStorage.executionHookspopulated outside of the branch-logic.