-
Notifications
You must be signed in to change notification settings - Fork 389
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(gnovm): remove Get prefixes from GetCallerAt, GetOrigSend, GetOrigCaller and extend abbreviations #3374
base: master
Are you sure you want to change the base?
refactor(gnovm): remove Get prefixes from GetCallerAt, GetOrigSend, GetOrigCaller and extend abbreviations #3374
Conversation
🛠 PR Checks Summary🔴 Changes to 'docs' folder must be reviewed/authored by at least one devrel and one tech-staff Manual Checks (for Reviewers):
Read More🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers. ✅ Automated Checks (for Contributors):🟢 Maintainers must be able to edit this pull request (more info) ☑️ Contributor Actions:
☑️ Reviewer Actions:
📚 Resources:Debug
|
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
@@ -22,7 +22,7 @@ Returns the **Address** field of the realm it was called upon. | |||
|
|||
#### Usage |
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.
missing modification in struct + subtitle name func
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.
done
docs/reference/stdlibs/std/chain.md
Outdated
``` | ||
--- | ||
|
||
## GetOrigPkgAddr | ||
## GetOriginPkgAddr |
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.
GetOriginPkgAddress
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.
done
``` | ||
--- | ||
|
||
## TestSetOrigPkgAddr | ||
## TestSetOriginPkgAddr |
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.
Why you "Addr" and sometimes "Address" which one is good, we should try to keep it consistent
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.
Address is good :) this is the missing refactor
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.
done
@@ -7,7 +7,7 @@ func ExampleExposeBankForMaketxRunOrImports() {} | |||
func ExampleCustomTellerImpl() {} | |||
func ExampleAllowance() {} | |||
func ExampleRealmBanker() {} | |||
func ExamplePrevRealmBanker() {} | |||
func ExamplePreviousRealmBanker() {} |
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.
should we limit the scope of the PR to change naming in std lib only
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.
This is related to Realm so I think we should change also here
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.
Done
While changing the Taking Gnoswap as an example, once a contract is deployed, it becomes practically impossible to modify1. This means there would be no way to adapt if these method names change, which could lead to fatal issues in production evironments. Therefore, I propose the following gradual approach:
This approach would allow existing projects adequate time to apply to the new changes. Also, I think this PR must mark as a breaking change BTW. Footnotes
|
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.
Looks good to me 👍
..
This is part of the std refactor that we're in the works for, for which we cannot avoid breaking backwards compatibility unfortunately.
Linked to #1475
This is a BREAKING CHANGE.