Skip to content

Conversation

@Jon-edge
Copy link
Collaborator

@Jon-edge Jon-edge commented Mar 6, 2024

Conversion tracking was broken in some cases. Wrong values, including our very ambiguous pluginId, were being used to calculate dollar conversion values. As a result, logEvent either silently failed without sending out the tracking event, or reported the incorrect amount values.

Refactor tracking in general, introduce an MVP of CryptoAmount, and make props more explicit. All of those combined ought to reduce the likelihood of similar future mistakes.

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)

@Jon-edge Jon-edge force-pushed the jon/fix/conversion-tracking branch from b51f2bf to 764b37c Compare March 9, 2024 01:20
Copy link
Contributor

@swansontec swansontec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking really good now!

We need to do a few more changes, so go ahead and squash the fixups before you do your final round of changes.

currencyConfig: wallet.currencyConfig
})

const { tokenId, nativeAmount } = cryptoAmount
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oooh, nice. Your new class may be even more useful than I expected. I like where this is going.

@Jon-edge Jon-edge force-pushed the jon/fix/conversion-tracking branch 2 times, most recently from c0a8c68 to 16d1a93 Compare March 12, 2024 01:48
We call everything `pluginId,` making things ambiguous and confusing when we pass `pluginId` around. In this case it was causing problems with the logging when treating a provider's pluginId as a wallet pluginId.

Also refactor reported data to be more explicit about what values mean.
…ll everything `pluginId,` making things ambiguous and confusing when we pass `pluginId` around. In this case it was causing problems with the logging when treating a provider's pluginId as a wallet pluginId.
@Jon-edge Jon-edge force-pushed the jon/fix/conversion-tracking branch from 16d1a93 to 782af1d Compare March 12, 2024 18:18
@Jon-edge Jon-edge merged commit a12db08 into develop Mar 12, 2024
@Jon-edge Jon-edge deleted the jon/fix/conversion-tracking branch March 12, 2024 18:19
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.

3 participants