-
Notifications
You must be signed in to change notification settings - Fork 29
[1/n permissions] chore: remove existing permissions system #67
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
Conversation
e069b7a to
73e57f3
Compare
72be4f4 to
aeb416b
Compare
adamegyed
left a comment
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.
This seems to be a duplicate of #65, but with the change of also removing the permitted calls in the fallback / native function path. We should rebase this onto that, because #65 also updates some of the tests that are commented out here.
For removing the permitted call flow, I'm OK to do that here, but note that once we remove that, any write-protected execution function (i.e. not marked as public) will no longer be callable via its original interface, they will need to go through the executeWithAuthorization path. We can always add permitted calls back if we think it's necessary.
c872746 to
83a2ddb
Compare
a1c31ce to
3941060
Compare
83a2ddb to
4d2390b
Compare
3941060 to
ee0a657
Compare
107f7bf to
5d439e8
Compare
0aefb0f to
c9fcabf
Compare
5d439e8 to
46dd1b2
Compare
46dd1b2 to
db9960f
Compare
adamegyed
left a comment
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.
Looks good! Just have 1 nit
|
addresses: erc6900/resources#50 |
Changelog:
callPermittedandpermittedExternalCallsfrom the account and the plugin manifest