Skip to content

Standard reference to ETH_SWAPS_TOKEN_ADDRESS via ETH_SWAPS_TOKEN_OBJECT.address#10613

Merged
danjm merged 1 commit intodevelopfrom
swaps-eth-address-constant-usage
Mar 9, 2021
Merged

Standard reference to ETH_SWAPS_TOKEN_ADDRESS via ETH_SWAPS_TOKEN_OBJECT.address#10613
danjm merged 1 commit intodevelopfrom
swaps-eth-address-constant-usage

Conversation

@danjm
Copy link
Copy Markdown
Contributor

@danjm danjm commented Mar 9, 2021

Currently, there are two ways to check whether an swaps token address is the ETH address. In some places we directly check against the ETH_SWAPS_TOKEN_ADDRESS, and in other places we check against ETH_SWAPS_TOKEN_OBJECT.address. This PR standardizes this to check against ETH_SWAPS_TOKEN_OBJECT.address in all places.

@danjm danjm requested a review from a team as a code owner March 9, 2021 11:17
@danjm danjm requested a review from NiranjanaBinoy March 9, 2021 11:17
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 9, 2021

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

brad-decker
brad-decker previously approved these changes Mar 9, 2021
@danjm danjm force-pushed the swaps-eth-address-constant-usage branch from a0dce6c to 75ac4b9 Compare March 9, 2021 14:26
@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [75ac4b9]
Page Load Metrics (644 ± 33 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint479565115
domContentLoaded4087436426933
load4097446446933
domInteractive4087436426933

@danjm danjm merged commit c86ceac into develop Mar 9, 2021
@danjm danjm deleted the swaps-eth-address-constant-usage branch March 9, 2021 15:59
@github-actions github-actions bot locked and limited conversation to collaborators Mar 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants