This repository was archived by the owner on May 26, 2026. It is now read-only.
feat: functional install scripts and fixed an issue with system callers.#2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request makes significant changes to how the StorageManager module is deployed and installed in the contracts package. The main update is the replacement of the previous manual, multi-step deployment script with a new, simpler deployment script that uses a single module contract. Additionally, there are minor configuration and code cleanup changes.
Deployment and Installation Changes:
DeployStorageManagerModule.s.solthat deploys theStorageManagerModuleand installs it as a root module in the World contract, simplifying the deployment and installation process.InstallStorageManager.s.solscript that manually deployed and registered multiple systems and tables, as this is now handled by the new module-based approach.Configuration and Code Cleanups:
WORLD_ADDRESSin the.env.pyropeconfiguration file to a new address.sm_v0_2_0__getStoreProxyAddressinConfigureSSU.s.sol.mud.config.ts[1] [2].