feat: link refactor#71
Draft
ChrisAmora wants to merge 1 commit into
Draft
Conversation
ChrisAmora
force-pushed
the
feat/link-v2
branch
2 times, most recently
from
989ac55 to
8752a72
Compare
Collaborator
|
You may want to leave the existing changesets instead of replacing them. Think about an easy to use directory structure that would be intuitive for users to use. Perhaps something link We will also want to consider how to handle different chains |
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request updates the test setup for MCMS and LinkToken contract deployments to use a new changeset and data source approach, removing reliance on the AddressBook and instead using the DataStore for contract address resolution. The changes improve consistency with the new deployment flow and clean up legacy code.