Skip to content

Fix "initilize" typo in V1/V2 interface NatSpec #33

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.

Sign up for GitHub

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

Merged
thedavidmeister merged 1 commit into from
May 31, 2026
Merged

Fix "initilize" typo in V1/V2 interface NatSpec #33

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/interface/ICloneableV2.sol
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ interface ICloneableV2 {
/// `ICloneableV2` MUST take appropriate measures to ensure that functions
/// called before initialize are safe to do so, or revert.
///
/// To be fully generic, `initilize` accepts `bytes` and so MUST ABI decode
/// To be fully generic, `initialize` accepts `bytes` and so MUST ABI decode
/// within the initialize function. This allows a single factory to service
/// arbitrary cloneable proxies but also erases the type of the
/// initialization config from the ABI. As tooling will inevitably require
Expand Down
2 changes: 1 addition & 1 deletion src/interface/deprecated/ICloneableV1.sol
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ interface ICloneableV1 {
/// `ICloneableV1` MUST take appropriate measures to ensure that functions
/// called before initialize are safe to do so, or revert.
///
/// To be fully generic `initilize` accepts `bytes` and so MUST ABI decode
/// To be fully generic `initialize` accepts `bytes` and so MUST ABI decode
/// within the initialize function. This allows the factory to service
/// arbitrary cloneable proxies but also erases the type of the
/// initialization config from the ABI. One workaround is to emit an event
Expand Down
Loading