* Reduce the amount of calls to insight snaps
* Add dep
* Update LavaMoat policies
* Fix selectors and revert changes to hook
* Remove dep
* Revert "Update LavaMoat policies"
This reverts commit 7469c94e0e7c52eb877766a96005cc559c9d8d20.
* Enable "Add Popular Network" feature by default
* Fixing e2e tests
* Attempt to fix e2e tests
* Revert "Attempt to fix e2e tests"
This reverts commit d88e8944b8df8f7c3075753f8d8b3480439f8e30.
* Get e2e tests passing
Co-authored-by: Dan J Miller <danjm.com@gmail.com>
* Setting truncate to true by default
* Updating readOnly to not have a focus state
* Updating focus state to be browser outline default
* Removing default args so storybook doesn't become out of sync with default props
* Updating outline CSS
* Adding TextField component
* Fixing lint issues
* More linting fixes
* Adding more tests
* Adding reference to TextFieldBase props
* Adding reminder todo comment to styles
* Using short hand syntax for conditionally firing event props and removing some css and unused classsNames in favor of box props
* Fixing up my sloppy code
* Removing text base docs update
* More clean up
* Adding more stories and docs
* Adding new stories to mdx docs
* Remove ETH badge from NetworkAccountBalanceHeader when on non-ETH networks
* Network specific icons, or fallback, in the network-account-balance-header
* Update snapshots
* Code cleanup
Co-authored-by: Dan Miller <danjm.com@gmail.com>
* Updating controller dependency
* fix
* fix
* fix
* fix
* fixes
* Lavamoat auto
* Update URLs for phishing detection testcase
* update lavamoat files
* call phishingController.test synchronously again
* bump @metamask/controllers to v32.0.1
* lint
* update policy files
* bump controllers version again
* modify update phishing list strategy
* revert back to use isOutOfDate, but without blocking substream
* possible way to fix e2e tests?
* enable testing
* Remove promise return from setupController in background.js, as it is no longer used
* Ensure updatePhishingLists is called in MM contrller constructer, so that phishing lists are updated right away
Co-authored-by: seaona <mariona@gmx.es>
Co-authored-by: Alex <adonesky@gmail.com>
Co-authored-by: Dan Miller <danjm.com@gmail.com>
* Fix inputs that should allow decimals
* Update e2e test to cover inputting of decimals in advanced fields
* Update e2e test to cover inputting of decimals in advanced fields
* Fix e2e tests
* Add transaction activity log component
* Remove duplicate tx activity log snapshot.
* Convert tx breakdown row to tlr.
* Convert tx status component to tlr.
* Convert User Preferenced Currency Display test to tlr.
* Consolidate and convert user-preferenced-currency-input.test.js to tlr.
* Consolidate and convert user-preferenced-token-input test to tlr.
* new test and changed ui
* added bip32 test
* fixed linting and other errors
* changed description
* Bump test-snaps to latest and fix tests
* Fix error e2e
* Fix confirm e2e
* Remove balance
Co-authored-by: Frederik Bolding <frederik.bolding@gmail.com>
* updated tag component and stashed storyshot update
* updated styling for tags
* updated test component for tag
* updated tag styles as per figma
* updated borderRadius prop for tag
* removed unused import
* updated Tag component with labelProps
* updated README
* updated Typography with Tag
We use the `@keystonehq/bc-ur-registry` package for integration with
Keystone devices. This package is peculiar as it not only ships with
JavaScript files but also original TypeScript files. When we started
adding support for TypeScript into the build system, we realized that
the TypeScript files were apparently developed using a different
TypeScript config than we use and therefore resulted in errors in our
build process. So we added a patch which removed these TypeScript files
so that we would fall back to using the compiled JavaScript files. This
removed type information but fixed our build system.
Since then, we've bumped this package and the files we removed have
changed, so the patch is no longer valid. This commit recreates the
patch so that we no longer get warnings from `patch-package`.
This update includes fixes for our `block-ref` and `retry-on-empty`
middleware.
The `block-ref` middleware resolves the block reference `latest` to a
specific block number, the latest one we are aware of. This is meant to
protect against situations where the network gives inconsistent answers
for what the latest block number is due to some nodes being out-of-sync
with each other (this was a frequent problem years ago with Infura).
It was broken in that the `latest` resolution was failing, and we were
submitting an additional redundant request to Infura for each request.
The `retry-on-empty` middleware is meant to retry certain methods
when they return an empty response. This was also meant to deal with
network synchronization issues that were more common years ago. This
middleware works by making a "child" request over and over until either
a retry limit is reached, or a non-empty response is received.
It was broken in that the final response recieved was thrown away, so
it's as though the middleware was not used. Except that it did result
in additional redundant network requests.
As a result of this update we should see that the extension is more
resilient to certain network synchronization issues. But this is
difficult to test, and these issues may not happen in production
anymore today.
We should see a reduction in requests to Infura as well. This should
be easier to test.
* Add filter tag
* Fix tag
* test tag
* fix
* Changed tag
* Add test-e2e-chrome
* Filter by branch instead of tag
* Move tests to correct mv3 folder
* Remove ignore from e2e regular chrome job
* Remove filter, so it's run on all PRs
* Handling red X for MV3 e2e failures
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
We now use the `latest` tag for the phishing warning page, we now use
the version that matches what we have in our manifest. This ensures
that our phishing warning e2e tests match the behaviour of the
production build, and it ensures that breaking changes to the phishing
warning page don't impact users in production.
