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

Underbridge: Drop updated dApp connections feature flag, further Taho renames #3595

Merged
merged 3 commits into from
Aug 15, 2023

Conversation

Shadowfiend
Copy link
Contributor

@Shadowfiend Shadowfiend commented Aug 4, 2023

This PR does two things:

  • Drops the ENABLE_UPDATED_DAPP_CONNECTIONS feature flag completely, as well as all related code paths.
  • Updates all remaining references to tally in the window provider to say taho instead, except if they were part of a publicly-visible API. In the latter case, adds a taho equivalent, so that we can phase tally out at an unspecified later date.

Latest build: extension-builds-3595 (as of Tue, 15 Aug 2023 20:01:43 GMT).

@Shadowfiend Shadowfiend changed the base branch from main to dappstrosities August 4, 2023 21:16
Base automatically changed from dappstrosities to main August 9, 2023 03:21
@Shadowfiend Shadowfiend marked this pull request as ready for review August 10, 2023 20:34
It is enabled and shall remain so!
Anything that is public API is duplicated as tally and taho, everything
else is renamed. Some string constants still say tally_ as checking for
breakage requires some extra diligence.:
@Shadowfiend
Copy link
Contributor Author

Did some light testing here with dApp connections across a few places, including stake.lido.fi which has direct Taho support. All working well, so going to ship it.

@Shadowfiend Shadowfiend merged commit 169c8ed into main Aug 15, 2023
6 checks passed
@Shadowfiend Shadowfiend deleted the underbridge branch August 15, 2023 20:49
@Shadowfiend Shadowfiend mentioned this pull request Aug 15, 2023
Copy link
Contributor

@hyphenized hyphenized left a comment

Choose a reason for hiding this comment

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

Code looks good, just one minor comment

providers: dedupedProviders,
shouldSetTallyForCurrentProvider(
shouldSetTally: boolean,
shouldReload = false
) {
if (shouldSetTally && this.currentProvider !== this.tallyProvider) {
this.currentProvider = this.tallyProvider
this.shouldSetTahoForCurrentProvider(shouldSetTally, shouldReload)
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we have to keep shouldSetTallyForCurrentProvider as an alias?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I went back and forth on this one--it was designed for internal calls, and I'm not sure why a third party would call it. But, it is strictly speaking public API, because it needed to be for us to access it in the first place. I felt safe nixing it since the integrations that do exist are provider-style and wouldn't need this call...

With that said, if you'd feel more comfortable with an alias sticking around, I'll slip it in.

Shadowfiend added a commit that referenced this pull request Aug 17, 2023
## Highlights

- Further performance improvements.
- Groundwork to rename backend dApp connection things (for the provider)
to Taho naming.

## What's Changed
* v0.46.1 by @Shadowfiend in
#3598
* Updates to release checklist: Removed Mintkudos test by @andreachapman
in #3600
* Revert "Revert "Debounce dispatched state diffs"" by @hyphenized in
#3579
* Underbridge: Drop updated dApp connections feature flag, further Taho
renames by @Shadowfiend in
#3595


**Full Changelog**:
v0.46.1...v0.47.0

Latest build:
[extension-builds-3601](https://github.com/tahowallet/extension/suites/15160003504/artifacts/866327987)
(as of Wed, 16 Aug 2023 19:09:51 GMT).
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