You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current version of the initializer modifier includes some logic for backwards compatibility that was added in #3450, which was in fact a simplification of the backwards compatibility code introduced in #3344.
We should consider further simplifications that break backwards compatibility for 5.0.
Haven't thought about this yet but it would probably come down to making initializer exactly equivalent to reinitializer(1). This means that instead of:
Note: In #3344 it is explained that the isConstructor exception was added back (after removal in 4.0) in order to use the initializer modifier to disable the initialization of implementation contracts with the following pattern:
The current version of the
initializer
modifier includes some logic for backwards compatibility that was added in #3450, which was in fact a simplification of the backwards compatibility code introduced in #3344.We should consider further simplifications that break backwards compatibility for 5.0.
Haven't thought about this yet but it would probably come down to making
initializer
exactly equivalent toreinitializer(1)
. This means that instead of:openzeppelin-contracts/contracts/proxy/utils/Initializable.sol
Lines 85 to 88 in d59306b
the code should look more like:
openzeppelin-contracts/contracts/proxy/utils/Initializable.sol
Line 119 in d59306b
The text was updated successfully, but these errors were encountered: