-
Notifications
You must be signed in to change notification settings - Fork 203
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(world): generate system libs #3587
Conversation
🦋 Changeset detectedLatest commit: 6501cd8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
92dbd65
to
243ad76
Compare
be9a773
to
4bd5065
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.
lgtm in general but maybe I would keep calldata args and fix at the system lib gen
packages/world/src/modules/init/implementations/StoreRegistrationSystem.sol
Outdated
Show resolved
Hide resolved
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.
leaving an initial review with a few questions but will look in more detail later
@@ -25,7 +26,7 @@ import { WorldRegistrationSystem } from "./WorldRegistrationSystem.sol"; | |||
* @author MUD (https://mud.dev) by Lattice (https://lattice.xyz) | |||
* @dev This contract provides functionality for the registration of store-related resources within the World framework. | |||
*/ | |||
contract StoreRegistrationSystem is System, IWorldErrors, LimitedCallContext { | |||
abstract contract StoreRegistrationSystem is System, IWorldErrors, IStoreRegistration, LimitedCallContext { |
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.
wdyt of always inheriting from interfaces first? not really an issue in this case but feels cleaner to me in the sense that interfaces go before implementations (that might implement some of the interface functions).
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.
I don't feel strongly. Does it impact anything on the compiler side?
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.
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.
Co-authored-by: V <[email protected]>
8232356
to
9ebebb7
Compare
pulled out of #3586