forked from protofire/rootstock-wallet-web
-
Notifications
You must be signed in to change notification settings - Fork 0
Rootstock stg #4
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
Open
gofman8
wants to merge
1,446
commits into
DistributedCollective:rootstock-stg
Choose a base branch
from
protofire:rootstock-stg
base: rootstock-stg
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Rootstock stg #4
gofman8
wants to merge
1,446
commits into
DistributedCollective:rootstock-stg
from
protofire:rootstock-stg
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0a91e39 to
6099b69
Compare
* feat(ColorCodedTxAccordion): add data-testid attribute to transaction details typography * feat(SplitMenuButton): add data-testid attributes for testing * fix(constants): update bridge widget URL for correct routing * feat(CreateTx): add combo button and selection functionality * feat(BatchTransaction): refactor addToBatch function to work with the combo button * fix(SplitMenuButton): ensure menu closes after option selection, even if the option does not change * fix: update snapshots
* feat: Add lend page, consent banner and geoblocking * fix: Display raw values for VaultDeposit in confirmation view * feat: Display raw redeem decoded data * refactor: Rename lend to earn * feat: Add deposit confirmation view * feat: Add redeem confirmation view * feat: Add deposit and redeem to txSummary * feat: Add deposit and redeem to txDetails * feat: Add Earn dashboard banner * fix: Hydration error on dashboard * feat: Add Earn info view * fix: Add temporary fix for missing cgw implementation * fix: Format values on the frontend * fix: Add powered by morpho logo * fix: Add earn info benefits * fix: Add widget fee tooltip, hide 0 fractions * fix: Add New tag in the sidebar * fix: Add tx tracking and adjust earn info * fix: Compress earn image and use inline sx * fix: Update snapshots * fix: Add decimals to TokenAmount for correct value shown * chore: Add prod widget url * fix: Add earn events * fix: Remove new tag from Bridge navigation point * fix: Add explicit event when navigating to earn via sidebar * fix: Add earn icon, update stake icon for dark mode * fix: Update earn info view title and spacings * refactor: Use feature flag, resolve TODO, rename lend to earn * fix: Add geoblocking check for earn hook * fix: Add prod widget url and limit chain ids * fix: Update spaces dashboard banner layout
* feat(TxSimulation): add nested transaction simulation support * fix(TxDetails): change import to type for SafeTransaction * feat(NestedTransaction): enhance UI with Card component * fix: add space before simulation block * fix(Nested transactions): use correct Safe info + executionOwner params for simulation of nested transactions (#5769) * fix(NestedTransaction): ensure nested transaction is approveHash call before calculating signedHash Render nested transaction link only if signedHash is defined * fix(useSignedHash): update dependency array to include full txData for memoization * feat(ExecTransaction): add simulation feature for nested transactions in confirmation view * fix(ExecTransaction): wrap link in Box component for improved layout
…sactions (#5756) --------- Co-authored-by: schmanu <manu@safe.global>
…ual to limit (#5866)
… (#5897) * fix: do not mark address book addresses as untrusted in NameChip * fix: optimization * fix: prioritize address book name
For an execTransaction call we don't have all the data required to display the full nested transaction with the advanced tx details. That is why e.g. the nonce is showing as -1 and when switching to the JSON tab in the receipt, we get an error. For that reason, we update the nestedTransaction display for execTransaction calls to use the TxData component instead of Summary.
…#5889) * Feat(Mobile): Add morpho vault decoding for transactions in history * fix: Update snapshots
* fix(tests): regression test tx_history_4 * fix(tests): format --------- Co-authored-by: Liliya Soroka <liliya.soroka@gmail.com>
* Fix(Earn): Align vault name with icon * fix: Update snapshots
* update How to title for recovery * add view tx details for multisend * fix nestedsafe tx creation * added a few more functions for the future advance details tests * add Call to line review to the tests * remove only
* fix: Hide signer form for proposers and select proposer address * fix: Allow proposal and execution/sign through parent safe * fix: Only show proposer wallet if its a tx creation
* feat(web): batch signer management * feat: add confirmation view component and undo rename * fix: remove unused helper * fix: remove unnecessary check * fix: nested test * fix: add warning and tracking * feat: add overview of added/removed owners * fix: add margin * fix: add padding to Signers component for improved layout --------- Co-authored-by: Pooya Raki <pooya.raki@gmail.com>
…n view (#5935)
* fix(Signing UX): remove duplicate spending limit info on confirmation view
- Updated ReviewTransactionContent and ConfirmationView to accept a new optional prop `withDecodedData` to control the display of decoded transaction data.
- Modified ReviewSpendingLimit to pass `withDecodedData={false}` to ReviewTransaction, ensuring decoded data is not shown in this context.
* tests(e2e): fix data-testid for spending limit beneficiary
- Added Box component with data-testid around the EthHashInfo for the beneficiary address to make sure the data-testid is in the DOM
* tests(snapshot): update snapshot
* fix: only fetch the balance for the active chain * fix: only fetch all chains balance in the DataFetchProvider and the chains balance menu * refactor(mobile): change safe slice The safeSlice was storing an aggragated fiatbalance, but it was containing the safeInfo of one of the deployments of the safe. In a multisafe setup it meant that the safeInfo stored would be for example mainnet, yet we could be showing the sepolia deployment on the screen. This lead to subtle errors such as the threshold being wrong in some places of the app. The rafactoring now makes sure that we store all versions of safeInfo inthe safesSlice. We also have an extraReducer that is triggered whenever the safesGetOverviewForMany query runs. This way we can keep the state of the safeInfo always up to date. --------- Co-authored-by: Daniel Dimitrov <daniel.d@safe.global>
* fix(Signing UX): remove duplicate NFT transfer info Disable decoded data display in ReviewNftBatch component * tests(snapshot): update snapshot * fix(tests): update SettingsChange test to reflect new owner text
* feat(store): add hooks into the cgwClient lifecycle The Auth endpoint returns a response cookie. This cookie is automatically set by browsers, but this doesn’t work that way in React-Native context. Because of this we need to be able to intercept the requests and deal with the cookie ourselves. By providing those hooks (or „escape hatches“), we can hook into the request process and manage the hooks on the mobile side. * feat(mobile): handle response cookie * refactor: move delegate typedData struct to utils * feat(mobile): register delegate after key import * fix(mobile): fix crash when loading accounts data * fix(mobile): register for queue notifications We were not properly authenticating the user and this was leading to the user not being subscribed for push notifications for queue events * feat(mobile): use middleware for push notifications * refactor(mobile): simplify notification code * feat(mobile): create per safe notification subscriptions * fix(mobile): update account when adding a delegate * fix(mobile): linting and failing tests * feat(mobile): add global notification setting * fix(mobile): subscription to notifications is handled in middleware * fix(mobile): only update subscription if safe was subscribed for notifications * refactor(mobile): useGTW hook and registration should use same code * refactor(mobile): requestAndRegister helper Created a new requestAndRegister helper within useNotificationManager to consolidate permission checks and registration logic Reused this helper when enabling notifications, simplifying the permission prompt flow Applied the helper in toggleNotificationState to remove duplicated permission logic * refactor(mobile): getDelegateKeyId Added a reusable getDelegateKeyId helper in the mobile utilities package, providing a single location to construct delegate key IDs * refactor(mobile): getAccountType introduced a reusable helper to derive notification account type based on Safe owners and signers * fix(mobile): cleanup console.logs and comments * fix(mobile): linting * fix(mobile): wrong comment * fix(mobile): resolve rebase issues * fix(mobile): require cycle * fix(mobile): failing test * fix(mobile): remove useMyAccounts hook It was already removed but the branch rebase was not correct. * feat(mobile): add notification parser * fix(mobile): wrong variable used * feat(mobile): display push notifications on foreground * fix(mobile): remove useGTW * fix(mobile): go around circular dependencies issue * fix(mobile): failing tests * refactor(mobile): use strategy pattern in middleware
* Fix(Mobile): UI fixes + copy changes * Fix(Mobile): Align top tabs UI * Fix(Mobile): Allow select all network toggle when editing contact * Fix(Mobile): Add explorer link action in transaction details view * Fix: Lint and update snapshots * Fix: Move hook out of helper function * fix: lint
* feat(mobile): add tx history skeleton loading state - Introduced TxHistorySkeleton and TxHistorySkeletonItem components for improved loading experience in transaction history. - Updated TxHistoryList to utilize skeleton components for initial loading and pagination states. * test(mobile): enhance TxHistoryContainer tests with loading states - Updated mock safe address generation to use faker for better test variability. - Added tests for initial loading skeleton, pagination loading skeleton, and refresh behavior in TxHistoryContainer. - Ensured loading states are correctly displayed and handled during transaction loading and refreshing. * refactor(mobile): replace SectionList with Tabs.SectionList in TxHistoryList - Updated TxHistoryList component to use Tabs.SectionList for improved tabbed navigation. - Adjusted content container styles to enhance layout, including margin adjustments for better alignment. * refactor(mobile): memoize skeleton widths in TxHistorySkeletonItem - Updated TxHistorySkeletonItem to memoize random widths for skeleton components, improving rendering performance and maintaining a consistent appearance during loading states. * refactor: use RefreshControl and custom loading indicator for pull-to-refresh * refactor: optimize rendering in TxHistoryList with useMemo * test: fix tests by mocking Tabs.SectionList * test: enhance TxHistoryContainer tests for refresh functionality * test: fix TxHistoryContainer tests * test: fix TxHistoryContainer tests to include timeout settings for waitFor
* fix(mobile): display notification even when app in quit state * fix(mobile): improve performance by syncing the store only when necessary We were subscribing to any kind of store update, but were interested only in the contacts and chain data. By using the store middleware we make sure that we sync the state only when those slices change. * fix(mobile): require cycle * fix(mobile): deprecated messaging usage * fix(mobile): failing test due to new middleware
As a temporary workaround for stylus/stylus#2938 we ping to 0.64.0.
* Feat(Web Analytics) Add Mixpanel event tracking * Feat(Analytics) add Launch Location to Safe App Launched event * Feat(Analytics) fix test suite * Feat(Analytics) Add Mixpanel token to Build Pipeline * Feat(Analytics) Track full Safe Address, not sliced * Feat(Analytics) Add user properties * Feat(Analytics) Clean Code base * Feat(Analytics) use blockchain network instead of chain id * Feature(Analytics) remove safe app id from safe app launched event * Feat(Analytics) simplify tx data * Feat(Analytics) use safe chain info instead of useCurrentChain * Feat(Analytics) add hook useNetworksOfSafe * Feat(Analytics) remove unnecessary comments * Feat(Analytics) use Safe's network instead of connected network on Safe App Launched event * Feat(Analytics) Add IP Anonymization * Feat(Analytics) refactor current chain tracking for MixPanel * Feat(Analytics) clean up comments * Feat(Analytics) Consolidate user properties * Feat(Analytics) refactor mixpanelSetUserProperties to single property * Feat(Analytics) remove comments * Feat(Analytics) add EOA Wallet propoerties to common event properties * Feat(Analytics) only init mixpanel when user opted in to tracking * Feat(Analytics) Move checks to safe* functions * Feat(Analytics) remove mixpanel commonEventParams in favor of mixpanel.register * Feat(Analytics) remove unnecessary comment * Feat(Analytics) Clear more comments * Feat(Analytics) refactor MIXPANEL_TOKEN to const file * Feat(Analytics) adapt tests * Feat(Analytics) Make tests package version agnostic
…s, and adjust constants for Tenderly integration
…t footer typography alignment
feat: Trezor support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What it solves
Resolves #
How this PR fixes it
How to test it
Screenshots
Checklist