Skip to content

[init_module][i18n] upgrade init_module in doc #171

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

WGB5445
Copy link
Contributor

@WGB5445 WGB5445 commented Aug 6, 2025

No description provided.

…arified its role during module publishing and upgrading, and updated optional usage notes across English, Spanish, and Chinese documentation.
Copy link

vercel bot commented Aug 6, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
aptos-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 6, 2025 2:00pm

- When a module is published for the first time (i.e., the module does not exist on-chain), the VM will search for and execute the `init_module(account: &signer)` function.
- When upgrading an existing module that is already on-chain, the `init_module` function will NOT be called.
- The signer of the account that is publishing the module is passed into the `init_module` function.
- **This function must be private and not return any value.**

Choose a reason for hiding this comment

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

Let's also add that it should have no type parameters and other arguments other than a single signer?

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