Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
I
interface
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
LuckySwap
interface
Commits
9e7d59f1
Unverified
Commit
9e7d59f1
authored
Aug 07, 2023
by
Nate Wienert
Committed by
GitHub
Aug 07, 2023
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
chore: fix typecheck error due to jest and cypress overlapping types (#7101)
parent
2ccd228f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
0 deletions
+3
-0
universal-search.test.ts
cypress/e2e/universal-search.test.ts
+3
-0
No files found.
cypress/e2e/universal-search.test.ts
View file @
9e7d59f1
...
@@ -39,6 +39,9 @@ describe('Universal search bar', () => {
...
@@ -39,6 +39,9 @@ describe('Universal search bar', () => {
// this test is experiencing flake despite being correct, i can see the right value in DOM
// this test is experiencing flake despite being correct, i can see the right value in DOM
// but for some reason cypress doesn't find it, so adding retries for now :/
// but for some reason cypress doesn't find it, so adding retries for now :/
{
{
// @ts-ignore see https://uniswapteam.slack.com/archives/C047U65H422/p1691455547556309
// basically cypress has bad types due to overlap with jest and you just have to deal with it
// i tried removing jest types but still happens
retries
:
{
retries
:
{
runMode
:
3
,
runMode
:
3
,
openMode
:
3
,
openMode
:
3
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment