Simplifying configuration

This is a bit rambling, sorry about that. Feel free to edit this to clean it up and add more to it. Jest currently has 51(!!) configuration options, many of which overlaps or intentionally overrides other options. (CLI options are out of scope for this issue, but they are obviously very much related) They fall into a few different categories: - file matching - some are arrays, some are not. - some are globs, some are regexes - `collectCoverageFrom` - `coveragePathIgnorePatterns` - `forceCoverageMatch` - `modulePathIgnorePatterns` - `testMatch` - `testPathIgnorePatterns` - `testRegex` - `transformIgnorePatterns` - `unmockedModulePathPatterns` - `watchPathIgnorePatterns` - modules and mocking - confusing overlap with node's `require` api (node paths, extensions) - `resetMocks` vs `clearMocks` vs `restoreMocks` - `automock` - `moduleDirectories` vs `modulePaths` (I honestly have no idea) - Coverage things - reporters - thresholds - output directory - Setup files - confusingly named, and inconsistent if they take array or string (#7119) - it keeps going (feel free to edit) --- First of all, I'd like to simplify the file matching a lot. Both to make it easier to use, but also easier to implement and reason about. For file matching I think `coveragePatterns: Array<Glob>`, `testPatterns: Array<Glob>`, `transformPatterns: Array<Glob>` and remove everything else. You can use negated patterns to exclude things ins

Posted by SimenB on Oct 16, 2018, 4:28 PM

Tags

• onboarding (Other)

Related issues

• I just invented a simple upgrade script for my father's ancient Fedora install.
• Weekly limit is draining like the old 5-hour limit
• Rather people unable to setup a static websites where needed.
• Besides the general awfulness of Windows that you describe, have you looked at C:\Windows recently?
• Does your work involves using teams or ms office or docker?
• Meta: Sorry, no response was returned