Skip to content
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

Review migration process #512

Draft
wants to merge 13 commits into
base: refactor/multi-chain-support-frontend
Choose a base branch
from

Conversation

truemiller
Copy link
Collaborator

Proposed changes

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

@truemiller truemiller changed the base branch from feat/allow-multiple-services-middleware to refactor/multi-chain-support-frontend November 28, 2024 12:24
- The CantMigrateAlert component in the StakingContractSection folder has been updated to use the useServiceBalances hook to retrieve service balances.
- The selectedService and isSelectedStakingContractDetailsLoaded variables are now used in the component.
- The serviceStakedOlasBalance variable has been added to calculate the required staked OLAS balance.
- The masterSafeBalanceRecord variable has been renamed from safeBalance and is used to calculate the required OLAS deposit.
- The nativeTokenSymbol variable is now calculated using the evmHomeChainId from the selectedAgentConfig.
- The requiredNativeTokenDeposit calculation has been updated to use the masterSafeBalanceRecord instead of safeBalance.

refactor: update ManageStakingPage component to use selectedStakingProgramId

- The ManageStakingPage component has been updated to use the selectedStakingProgramId variable from the useStakingProgram hook.
- The currentStakingProgramId variable has been removed.
- The stakingProgramIdsAvailable variable is now calculated using the selectedAgentConfig.evmHomeChainId and the STAKING_PROGRAMS object.
- The stakingProgramId comparison in the map function has been updated to use selectedStakingProgramId instead of currentStakingProgramId.
- The isActiveStakingProgramLoaded check has been updated to use selectedStakingProgramId instead of activeStakingProgramId or defaultStakingProgramId.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants