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

refactor: Use near_sdk::store instead of the legacy near_sdk::collections #7

Merged
merged 3 commits into from
Feb 24, 2024

Conversation

njelich
Copy link
Contributor

@njelich njelich commented Feb 14, 2024

The example implementation used a legacy collection, instead of the newer ones located in near-sdk::store. I updated the implementation, and cleaned up feature flags.

Should I add the wee_alloc feature as well?

Copy link
Collaborator

@frol frol left a comment

Choose a reason for hiding this comment

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

I believe wee_alloc should only be disabled if you want to manually specify some other allocator. This is definitely not what we want to do in the simple starter app.

Cargo.toml Outdated Show resolved Hide resolved
@frol frol changed the title removed legacy collection, updated near-sdk-rs feature flags refactor: Use near_sdk::store instead of the legacy near_sdk::collections Feb 24, 2024
@frol frol merged commit f14289e into near:main Feb 24, 2024
3 of 4 checks passed
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