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

chore(near-primitives): document why FunctionCallPermission::receiver_id != AccountId #4773

Merged
merged 4 commits into from
Sep 6, 2021

Conversation

miraclx
Copy link
Contributor

@miraclx miraclx commented Sep 1, 2021

Resolves #4739: documents why the receiver_id field in FunctionCallPermission isn't an AccountId despite recently refactoring the whole workspace to using strict AccountId-s.

See #4621 (comment) for more context

@frol
Copy link
Collaborator

frol commented Sep 1, 2021

@miraclx Thanks for landing these code quality improvements!

core/primitives-core/src/account.rs Outdated Show resolved Hide resolved
Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
@near-bulldozer near-bulldozer bot merged commit 9abfeed into near:master Sep 6, 2021
@miraclx miraclx deleted the doc-no-accountid-in-fncallperm branch September 6, 2021 13:17
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.

Explain why FunctionCallPersmission doesn't use AccountId
4 participants