-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add acl to near-token-contract #20
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.
I skimmed over the PR and it looks good. Let me give a second review.
In the meantime can you resolve conflicts?
It allowed some cleanups thanks to recent updates in near-plugins.
The conflicts are resolved and the dependencies (near-plugins, workspaces) updated. |
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.
Made several changes including the functions to the factory in: #24. Please take a look to merge it here, then to master
.
What's new: Made the changes proposed in #24 and cleaned up several things (see commit messages for details). |
Adds access control based on
near-plugins
tonear-token-contract
.Running the following test verifies that access control is set up correctly:
If other developers using the acl plugin are expected to write similar tests, we might consider exporting test helpers from
near-plugins
. Something similar to this.