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

Create new package for TallyHo name change to Taho #1542

Merged
merged 8 commits into from
Mar 7, 2023

Conversation

Adamj1232
Copy link
Member

@Adamj1232 Adamj1232 commented Feb 21, 2023

Description

The rename request TallyHo -> Taho came from the Tally team on a rebrand that has occurred

Updated wallet name, docs and readme-s to make note of this (I don't think creating a new package is justified at this point and would be confusing and a pain for DApps who currently support Tally/Taho)

Screen Shot 2023-02-21 at 11 00 47 AM

Screen Shot 2023-02-21 at 11 00 38 AM

Request from Taho team:
Screen Shot 2023-02-21 at 11 20 11 AM

Checklist

  • The version field in package.json of the package you have made changes in is incremented following semantic versioning and using alpha release tagging
  • The box that allows repo maintainers to update this PR is checked
  • I tested locally to make sure this feature/fix works
  • I have run yarn file-check, yarn type-check & yarn build to confirm there are not any associated errors
  • This PR passes the Circle CI checks

@vercel
Copy link

vercel bot commented Feb 21, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
web3-onboard-docs ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Mar 6, 2023 at 9:59PM (UTC)

@taylorjdawson
Copy link
Contributor

@Adamj1232 I think they may want the package name to change? 🤔 Should we double check? It would be simple enough I suppose and then on the old tallyho package we could show it is deprecated? Or even use this?

@Adamj1232
Copy link
Member Author

@Adamj1232 I think they may want the package name to change? 🤔 Should we double check? It would be simple enough I suppose and then on the old tallyho package we could show it is deprecated? Or even use this?

@taylorjdawson Yeah that is a good question and we discussed it yesterday in the planning meeting. Im waiting to hear back from the Tally/Taho team on this so we will see what their response is. Their initial request was to just update the displayed wallet name, but its prob best to create a new package and deprecate Tally

@Adamj1232 Adamj1232 changed the title Rename TallyHo wallet name to Taho Create new package for TallyHo name change to Taho Mar 6, 2023
Copy link
Contributor

@leightkt leightkt left a comment

Choose a reason for hiding this comment

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

I think creating a new package makes sense. Looks good!

@Adamj1232 Adamj1232 merged commit 4226d71 into develop Mar 7, 2023
@Adamj1232 Adamj1232 deleted the update_rename_tally_to_taho branch March 7, 2023 00:00
hlopes-ledger pushed a commit to hlopes-ledger/web3-onboard that referenced this pull request Mar 10, 2023
* Rename TallyHo wallet name to Taho

* Remove commented out code

* Remove unneeded file

* Refine deploy script

* Revert docs changes

* Update more docs

* Add Taho docs and fix connect wallet button issue
Adamj1232 added a commit that referenced this pull request Mar 14, 2023
* yarn latest packages

* Temporarily remove infinity wallet

* Fix/sitemap (#1565)

* update root path
* Update the sitemap generation

* Create new package for TallyHo name change to Taho (#1542)

* Rename TallyHo wallet name to Taho

* Remove commented out code

* Remove unneeded file

* Refine deploy script

* Revert docs changes

* Update more docs

* Add Taho docs and fix connect wallet button issue

* [core, react, vue]: Fix - Remove wallet from localStorage when disconnect is called with the primary wallet label (#1566)

* Add removal of localstorage wallet string on disconnect

* Add check to confirm the disconnected wallet is also the primary/current wallet

* Revert demo change

* Fix sitemap (#1573)

* SvelteKit+Vite - Fix config issue with sveltekit and vite config - Add docs (#1569)

* Fix config issue with sveltekit and vite config

* Update package.json

* Add examples to docs

* Fix funk formatting

* Add more notes around sveltekit+vite config and pnpm usage

* [walletconnect-v2.3.1-alpha.1]: Update - walletConnect params to include `requiredChains` and updated WC deps (#1574)

* Update wc package to the latest and parameterize required chains

* Update WC module to allow req chains as parameter

* Update docs

* Update docs

* Update package versions

* Fix wc package versioning (#1581)

---------

Co-authored-by: Aaron <abarnard@protonmail.com>
Co-authored-by: Taylor Dawson <taylorjdawson@gmail.com>
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.

4 participants