1
0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-11-29 15:50:28 +01:00
metamask-extension/ui/hooks/useEventFragment.js
MetaMask Bot 31d5c1cf22
Version v10.18.4 RC (#15643)
* Version v10.18.4

* Fix default currency symbol for `wallet_addEthereumChain` + improve warnings for data that doesn't match our validation expectations (#15201)

* set more appropriate default for ticker symbol when wallet_addEthereumChain is called

* throw error to dapp when site suggests network with same chainId but different ticker symbol from already added network, instead of showing error and disabled notification to user

* Fix Provider Tracking Metrics (#15082)

* fix filetype audit (#15334)

* Remove decentralized 4byte function signature registry since it contains incorrect signatures and we can't algorithmically check for best option when 4byte.directory is down (#15300)

* remove decentralized 4byte function signature registry since it is griefed and we can't algorithmically check for best option when 4byte is down

* add migration

* remove nock of on chain registry call in getMethodDataAsync test

* remove audit exclusion (#15346)

* Updates `eth-lattice-keyring` to v0.10.0 (#15261)

This is mainly associated with an update in GridPlus SDK and enables
better strategies for fetching calldata decoder data.
`eth-lattice-keyring` changes:
GridPlus/eth-lattice-keyring@v0.7.3...v0.10.0
`gridplus-sdk` changes (which includes a codebase rewrite):
GridPlus/gridplus-sdk@v1.2.3...v2.2.2

* Fix 'block link explorer on custom networks' (#13870)

* Created a logic for the 'Add a block explorer URL'

Removed unused message

Message logic rollback

Modified history push operation

WIP: Pushing before rebasing

Applied requested changes

Removed unintenionally added code

* Lint fix

* Metrics fixed

* Stop injecting provider on docs.google.com (#15459)

* Fix setting of gasPrice when on non-eip 1559 networks (#15628)

* Fix setting of gasPrice when on non-eip 1559 networks

* Fix unit tests

* Fix logic

* Update ui/ducks/send/send.test.js

Co-authored-by: Mark Stacey <markjstacey@gmail.com>

Co-authored-by: Mark Stacey <markjstacey@gmail.com>

* [GridPlus] Bumps `eth-lattice-keyring` to v0.11.0 (#15490)

* [GridPlus] Bumps `gridplus-sdk` to v2.2.4 (#15561)

* remove exclusions for mismatched object jsdoc type casing (#15351)

* Improve `tokenId` parsing and clean up `useAssetDetails` hook (#15304)

* Fix state creation in setupSentryGetStateGlobal (#15635)

* filter breadcrumbs for improved clarity while debugging sentry errors (#15639)

* Update v10.18.4 changelog (#15645)

* Auto generated changelog

* Update 10.18.4 changelog

* Run lavamoat:auto

* Call metrics event for wallet type selection at the right time (#15591)

* Fix Sentry in LavaMoat contexts (#15672)

Our Sentry setup relies upon application state, but it wasn't able to
access it in LavaMoat builds because it's running in a separate
Compartment.

A patch has been introduced to the LavaMoat runtime to allow the root
Compartment to mutate the `rootGlobals` object, which is accessible
from outside the compartment as well. This lets us expose application
state to our Sentry integration.

* Fix Sentry deduplication of events that were never sent (#15677)

The Sentry `Dedupe` integration has been filtering out our events, even
when they were never sent due to our `beforeSend` handler. It was
wrongly identifying them as duplicates because it has no knowledge of
`beforeSend` or whether they were actually sent or not.

To resolve this, the filtering we were doing in `beforeSend` has been
moved to a Sentry integration. This integration is installed ahead of
the `Dedupe` integration, so `Dedupe` should never find out about any
events that we filter out, and thus will never consider them as sent
when they were not.

* Replace `lavamoat-runtime.js` patch (#15682)

A patch made in #15672 was found to be unnecessary. Instead of setting
a `rootGlobals` object upon construction of the root compartment, we
are now creating a `sentryHooks` object in the initial top-level
compartment. I hadn't realized at the time that the root compartment
would inherit all properties of the initial compartment `globalThis`.

This accomplishes the same goals as #15672 except without needing a
patch.

* Update v10.18.4 changelog

* Fix lint issues

* Update yarn.lock

* Update `depcheck` to latest version (#15690)

`depcheck` has been updated to the latest version. This version pins
`@babel/parser` to v7.16.4 because of unresolved bugs in v7.16.5 that
result in `depcheck` failing to parse TypeScript files correctly.

We had a Yarn resolution in place to ensure `@babel/parser@7.16.4` was
being used already. That resolution is no longer needed so it has been
removed. This should resove the issue the dev team has been seeing
lately where `yarn` and `yarn-deduplicate` disagree about the state the
lockfile should be in.

* Update yarn.lock

* Update LavaMoat policy

* deduplicate

* Update LavaMoat build policy

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
Co-authored-by: Alex Donesky <adonesky@gmail.com>
Co-authored-by: Brad Decker <bhdecker84@gmail.com>
Co-authored-by: Alex Miller <asmiller1989@gmail.com>
Co-authored-by: Filip Sekulic <filip.sekulic@consensys.net>
Co-authored-by: Erik Marks <25517051+rekmarks@users.noreply.github.com>
Co-authored-by: Dan J Miller <danjm.com@gmail.com>
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
Co-authored-by: seaona <54408225+seaona@users.noreply.github.com>
Co-authored-by: seaona <mariona@gmx.es>
Co-authored-by: PeterYinusa <peter.yinusa@consensys.net>
2022-08-24 19:57:47 +01:00

101 lines
3.7 KiB
JavaScript

import { useCallback, useEffect, useRef, useState } from 'react';
import { useSelector } from 'react-redux';
import { getEnvironmentType } from '../../app/scripts/lib/util';
import { selectMatchingFragment } from '../selectors';
import {
finalizeEventFragment,
createEventFragment,
updateEventFragment,
} from '../store/actions';
import { useSegmentContext } from './useSegmentContext';
/**
* Retrieves a fragment from memory or initializes new fragment if one does not
* exist. Returns three methods that are tied to the fragment, as well as the
* fragment id.
*
* @param {string} existingId
* @param {object} fragmentOptions
* @returns
*/
export function useEventFragment(existingId, fragmentOptions = {}) {
// To prevent overcalling the createEventFragment background method a ref
// is used to store a boolean value of whether we have already called the
// method.
const createEventFragmentCalled = useRef(false);
// In order to immediately return a created fragment, instead of waiting for
// background state to update and find the newly created fragment, we have a
// state element that is updated with the fragmentId returned from the
// call into the background process.
const [createdFragmentId, setCreatedFragmentId] = useState(undefined);
// Select a matching fragment from state if one exists that matches the
// criteria. If an existingId is passed in it is preferred, if not and the
// fragmentOptions has the persist key set to true, a fragment with matching
// successEvent will be pulled from memory if it exists.
const fragment = useSelector((state) =>
selectMatchingFragment(state, {
fragmentOptions,
existingId: existingId ?? createdFragmentId,
}),
);
// If no valid existing fragment can be found, a new one must be created that
// will then be found by the selector above. To do this, invoke the
// createEventFragment method with the fragmentOptions and current sessionId.
// As soon as we call the background method we also update the
// createEventFragmentCalled ref's current value to true so that future calls
// are suppressed.
useEffect(() => {
if (fragment === undefined && createEventFragmentCalled.current === false) {
createEventFragmentCalled.current = true;
createEventFragment({
...fragmentOptions,
environmentType: getEnvironmentType(),
}).then((createdFragment) => {
setCreatedFragmentId(createdFragment.id);
});
}
}, [fragment, fragmentOptions]);
const context = useSegmentContext();
/**
* trackSuccess is used to close a fragment with the affirmative action. This
* method is just a thin wrapper around the background method that sets the
* necessary values.
*/
const trackSuccess = useCallback(() => {
finalizeEventFragment(fragment.id, { context });
}, [fragment, context]);
/**
* trackFailure is used to close a fragment as abandoned. This method is just a
* thin wrapper around the background method that sets the necessary values.
*/
const trackFailure = useCallback(() => {
finalizeEventFragment(fragment.id, { abandoned: true, context });
}, [fragment, context]);
/**
* updateEventFragmentProperties is a thin wrapper around updateEventFragment
* that supplies the fragment id as the first parameter. This function will
* be passed back from the hook as 'updateEventFragment', but is named
* updateEventFragmentProperties to avoid naming conflicts.
*/
const updateEventFragmentProperties = useCallback(
(payload) => {
updateEventFragment(fragment.id, payload);
},
[fragment],
);
return {
trackSuccess,
trackFailure,
updateEventFragment: updateEventFragmentProperties,
fragment,
};
}