feat: L2Resolver state variables and constructor w/unit tests - #2
Conversation
EFI-425 constructor and variables
State Variables:
Constants:
|
| string public constant CHAIN_IDENTIFIER_EIP7930_KEY = 'chain.id.eip7930'; | ||
|
|
||
| /// @inheritdoc IL2Resolver | ||
| IENS public immutable ENS_REGISTRY; |
There was a problem hiding this comment.
@0xAustrian what do you think about the visibility of these variables? I went with public so I could unit test them. I kept _REVERSE_LOOKUP_NODE since it will be used in internal logic
There was a problem hiding this comment.
I would set everything on public tbh, even REVERSE_LOOKUP_NODE
|
|
||
| /** | ||
| * @title L2Resolver | ||
| * @author @defi-wonderland |
There was a problem hiding this comment.
do we usually set the author?
| @@ -0,0 +1,51 @@ | |||
| // SPDX-License-Identifier: MIT | |||
|
|
|||
| @@ -0,0 +1,51 @@ | |||
| // SPDX-License-Identifier: MIT | |||
|
|
|||
| pragma solidity ^0.8.30; | |||
There was a problem hiding this comment.
Let's use a fixed .sol version.
There was a problem hiding this comment.
I mean it's no big deal but a good practice to use the exact same version everywhere.
There was a problem hiding this comment.
This is so the CI does not fail, right? In that case I think we can temporarily comment the integration tests section in the workflow (sorry, forgot to mention that. It would have been a good addition to the PR#1).
🤖 Linear
Closes EFI-425
Closes EFI-434