Skip to content
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

Added Policy State Getters #122

Merged
merged 17 commits into from
Jan 23, 2025

Conversation

Dhruv-Mishra
Copy link
Contributor

@Dhruv-Mishra Dhruv-Mishra commented Jan 21, 2025

Added Policy State Getters for the policies defined here

Related to issue: #109

@Dhruv-Mishra Dhruv-Mishra marked this pull request as ready for review January 21, 2025 19:32
@Dhruv-Mishra Dhruv-Mishra changed the title Feat/alt policy state getters Added Policy State Getters Jan 22, 2025
@Dhruv-Mishra
Copy link
Contributor Author

Dhruv-Mishra commented Jan 22, 2025

@kopy-kat please review this, shifting the changes here from #119
I have also included Policy Contract Addresses within GLOBAL_CONSTANTS for now.
Not sure if this is the right move since I did not find the explicit use of these addresses outside of the policy folders.

userOpSender,
}: {
client: PublicClient
configId: bigint
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could also just accept this as a hex or is there a reason you're not doing this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just thought bigint would be the default way here.
Will update this to only include Hex

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I enforce configId being a Byte32 Hex or write functions to automatically extend any Hex argument to Hex32 or is it not required?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont think its required here

@kopy-kat kopy-kat merged commit 4b20285 into rhinestonewtf:main Jan 23, 2025
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants