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
merge status-message-collections #1076
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.
Hi! Unfortunately, this is not quite what we want here. We'd like there to be one status-message
contract using the LookupMap
.
LookupMap
is more efficient (in the NEAR blockchain context) and the appropriate storage option to choose in situations like these. Since examples need to show contract devs best practices, we really need to advertise it over HashMap
here.
Understood, making chnages. |
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.
LGTM!
@shariffdev One note: please include the phrase |
Addresses: #809
This PR eliminates the
status-message-collection
example, leaving only onestatus-message
-esque example.