-
Notifications
You must be signed in to change notification settings - Fork 47
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
refactored elcontracts and avsregistry builders to use wire dependency injection #297
Closed
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,8 +13,9 @@ help: | |
bindings: ## generates contract bindings | ||
cd contracts && rm -rf bindings/* && ./generate-bindings.sh | ||
|
||
mocks: ## generates mocks | ||
generate: ## generates mocks and wire files | ||
go install go.uber.org/mock/[email protected] | ||
go install github.com/google/wire/cmd/[email protected] | ||
go generate ./... | ||
|
||
tests: ## runs all tests | ||
|
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,121 @@ | ||
//go:build wireinject | ||
// +build wireinject | ||
|
||
package avsregistry | ||
|
||
import ( | ||
"github.com/Layr-Labs/eigensdk-go/chainio/clients/elcontracts" | ||
"github.com/Layr-Labs/eigensdk-go/chainio/clients/eth" | ||
"github.com/Layr-Labs/eigensdk-go/chainio/txmgr" | ||
"github.com/Layr-Labs/eigensdk-go/logging" | ||
"github.com/google/wire" | ||
) | ||
|
||
func NewReaderFromConfig( | ||
cfg Config, | ||
ethClient eth.Client, | ||
logger logging.Logger, | ||
) (*ChainReader, error) { | ||
wire.Build(NewBindingsFromConfig, NewChainReaderFromBindings) | ||
return &ChainReader{}, nil | ||
} | ||
|
||
// including here because needed in NewWriterFromConfig | ||
func NewElConfigFromAvsBindings( | ||
bindings *ContractBindings, | ||
) elcontracts.Config { | ||
return elcontracts.Config{ | ||
// TODO: missing RewardsCoordinatorAddr in bindings, because no other contract points to | ||
// RewardsCoordinator so bindings doesn't return that address... | ||
// Ways to fix this bug: | ||
// 1. Make some other contract point to RewardsCoordinator so we can get the address from bindings | ||
// 2. Pass RewardsCoordinatorAddr as a parameter to NewAVSRegistryContractBindings | ||
// 3. Pass RewardsCoordinatorAddr as a parameter to this function and NewWriterFromConfig | ||
DelegationManagerAddress: bindings.DelegationManagerAddr, | ||
AvsDirectoryAddress: bindings.AvsDirectoryAddr, | ||
} | ||
} | ||
|
||
func NewWriterFromConfig( | ||
cfg Config, | ||
ethClient eth.Client, | ||
txMgr txmgr.TxManager, | ||
logger logging.Logger, | ||
) (*ChainWriter, error) { | ||
wire.Build( | ||
NewBindingsFromConfig, | ||
NewElConfigFromAvsBindings, | ||
elcontracts.NewReaderFromConfig, | ||
wire.Bind(new(elcontracts.Reader), new(*elcontracts.ChainReader)), | ||
NewChainWriterFromBindings, | ||
) | ||
return &ChainWriter{}, nil | ||
} | ||
|
||
// Note that unlike reader/writer, a websocket eth client must be provided | ||
func NewSubscriberFromConfig( | ||
cfg Config, | ||
wsClient eth.Client, | ||
logger logging.Logger, | ||
) (*ChainSubscriber, error) { | ||
wire.Build(NewBindingsFromConfig, NewChainSubscriberFromBindings) | ||
return &ChainSubscriber{}, nil | ||
} | ||
|
||
type ClientsAndBindings struct { | ||
ChainReader *ChainReader | ||
ChainWriter *ChainWriter | ||
ChainSubscriber *ChainSubscriber | ||
ContractBindings *ContractBindings | ||
} | ||
|
||
// ============= Workaround Code ================= | ||
// this section is needed because wire does not allow a Build dependency graph | ||
// with two dependencies of the same type. See: | ||
// https://github.com/google/wire/blob/main/docs/faq.md#what-if-my-dependency-graph-has-two-dependencies-of-the-same-type | ||
// In BuildClientsFromConfig since both ethHttpClient and ethWsClient have type eth.Client, | ||
// we need to wrap one of them in a new type to avoid the error. | ||
type ethWsClient eth.Client | ||
|
||
func newEthWsClient( | ||
wsClient eth.Client, | ||
) ethWsClient { | ||
return (ethWsClient)(wsClient) | ||
} | ||
|
||
func newSubscriberFromConfigWithEthWsClientType( | ||
cfg Config, | ||
wsClient ethWsClient, | ||
logger logging.Logger, | ||
) (*ChainSubscriber, error) { | ||
return NewSubscriberFromConfig(cfg, eth.Client(wsClient), logger) | ||
} | ||
|
||
func buildClientsFromConfig( | ||
cfg Config, | ||
ethHttpClient eth.Client, | ||
ethWsClient ethWsClient, | ||
txMgr txmgr.TxManager, | ||
logger logging.Logger, | ||
) (*ClientsAndBindings, error) { | ||
wire.Build( | ||
NewBindingsFromConfig, | ||
NewReaderFromConfig, | ||
NewWriterFromConfig, | ||
newSubscriberFromConfigWithEthWsClientType, | ||
wire.Struct(new(ClientsAndBindings), "*"), | ||
) | ||
return &ClientsAndBindings{}, nil | ||
} | ||
|
||
// ============= End of Workaround Code ================= | ||
|
||
func BuildClientsFromConfig( | ||
cfg Config, | ||
ethHttpClient eth.Client, | ||
ethWsClient eth.Client, | ||
txMgr txmgr.TxManager, | ||
logger logging.Logger, | ||
) (*ClientsAndBindings, error) { | ||
return buildClientsFromConfig(cfg, ethHttpClient, ethWsClient, txMgr, logger) | ||
} |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
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.
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.
why do we need to couple these 2 generation? any particular reason or just to combine generation together?
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.
Is there a way to separate go generated stuff? Right now if we run go generate it just looks for all the go:generate comments in the repo and executed all of them. Maybe there’s a way to tag the generate commands with subtask names and get go generate to filter on those?