-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: use IterableMap for near contract #209
Conversation
…e/refactor-signature
…e/refactor-signature
4d7efca
to
becb428
Compare
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.
Nice! Why haven't we used this structure before? Probably because it’s not in collections.
From what I see, the only breaking change here is the SignatureResult part. Overall, I do not want to invest time in this API since it is unclear if we need it. Maybe we will rewrite it to work like the one on Ethereum, with a significantly simplified design.
We can afford breaking changes here now or after the release since technically we are not releasing on NEAR. We will need to fix some things in our infra and tooling, let's merge this if you are ok with that.
SignatureResult isn't a breaking change since it's only used within the contract |
The base branch was changed.
In the spirit of breaking changes, use
IterableMap
instead ofLookupMap
just so we don't maintain that pesky request counter anymore.