MetaMask / MetaMask/metamask-extension

chore: set separate configs for lint e2e (mocha) and jest

Open
#32,236 0 comments 0 reactions 0 assignees View on GitHub
team-extension-platform team-qa
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### What is this about?

Set separate configs for lint e2e (mocha) and jest. This is what the following PR intended, but it broke the lint validations for our test folder so it has been reverted

https://github.com/MetaMask/metamask-extension/pull/31049

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing reverted PR #31049 and the repository's current lint configuration and test-folder validation setup. Done means linting has separate configurations for the Mocha end-to-end tests and Jest, while the existing test-folder lint validations pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, typescript
Domain
testing-qa, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.