library-mirrors/jquery
1
0
Fork 0
mirror of https://github.com/jquery/jquery.git synced 2024-11-23 02:54:22 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
4a29888c75
jquery/test/.eslintrc.json

79 lines
1.4 KiB
JSON
Raw Normal View History

Build: Switch from jscs+jshint to eslint
2016-05-10 09:06:37 +00:00
{
Build: ESLint setup improvements 1. Use the short name of the preset in the config. 2. Run ESLint first on non-minified files. 3. Explicitly specify environments in every config file (those settings cascade which means we've been assuming a Node.js environment where we shouldn't have).
2016-11-02 23:51:34 +00:00
"root": true,
"extends": "../.eslintrc-browser.json",
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"env": {
Build: ESLint setup improvements 1. Use the short name of the preset in the config. 2. Run ESLint first on non-minified files. 3. Explicitly specify environments in every config file (those settings cascade which means we've been assuming a Node.js environment where we shouldn't have).
2016-11-02 23:51:34 +00:00
// In source the browser env is not enabled but unit tests rely on them
// too much and we don't run them in non-browser environments anyway.
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"browser": true
},
Build: ESLint setup improvements 1. Use the short name of the preset in the config. 2. Run ESLint first on non-minified files. 3. Explicitly specify environments in every config file (those settings cascade which means we've been assuming a Node.js environment where we shouldn't have).
2016-11-02 23:51:34 +00:00
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"globals": {
"require": false,
"Promise": false,
"Symbol": false,
"QUnit": false,
"ajaxTest": false,
"testIframe": false,
"createDashboardXML": false,
Selector: Inline Sizzle into the selector module: 3.x version (#5113) This commit removes Sizzle from jQuery, inlining its code & removing obsolete workarounds where applicable. The Sizzle AUTHORS.txt file has been merged with the jQuery one - people are sorted by their first contributions to either of the two repositories. The main `selector` module can be disabled in favor of `selector-native` via: grunt custom:-selector For backwards compatibility, the legacy `sizzle` alias is also supported (it will be dropped in jQuery `4.0.0`): grunt custom:-selector Sizzle tests have been ported to jQuery ones. Ones that are not compatible with the `selector-native` module are disabled if the regular selector module is excluded. Backwards compatibility is still kept for all `Sizzle` utils - they continue to be available under `jQuery.find` - but the primary implementation is now attached directly to jQuery. Some selector utils shared by `selector` & `selector-native` have been extracted & deduplicated. `jQuery.text` and `jQuery.isXMLDoc` have been moved to the `core` module. The commit reduces the gzipped jQuery size by 851 bytes compared to the `3.x-stable` branch. Closes gh-5113 Ref gh-4395 Ref gh-4406
2022-12-14 00:41:31 +00:00
"createWithFriesXML": false,
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"createXMLFragment": false,
Tests: Exclude tests based on compilation flags, not API presence (3.x version) Introduces a new test API, `includesModule`. The method returns whether a particular module like "ajax" or "deprecated" is included in the current jQuery build; it handles the slim build as well. The util was created so that we don't treat presence of particular APIs to decide whether to run a test as then if we accidentally remove an API, the tests would still not fail. Closes gh-5071 Fixes gh-5069 Ref gh-5046 (partially cherry picked from commit fae5fee8b435cc20352d28b0a384b9784b1ad9ed)
2022-07-12 15:12:27 +00:00
"includesModule": false,
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"moduleTeardown": false,
"url": false,
"q": false,
"jQuery": true,
"sinon": true,
"amdDefined": true,
"fireNative": true,
"Globals": true,
"hasPHP": true,
"isLocal": true,
"supportjQuery": true,
"originaljQuery": true,
"$": true,
"original$": true,
"baseURL": true,
"externalHost": true
},
Build: ESLint setup improvements 1. Use the short name of the preset in the config. 2. Run ESLint first on non-minified files. 3. Explicitly specify environments in every config file (those settings cascade which means we've been assuming a Node.js environment where we shouldn't have).
2016-11-02 23:51:34 +00:00
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"rules": {
// See https://github.com/eslint/eslint/issues/2342
"no-unused-vars": "off",
Build: Switch from jscs+jshint to eslint
2016-05-10 09:06:37 +00:00
Build: ESLint setup improvements 1. Use the short name of the preset in the config. 2. Run ESLint first on non-minified files. 3. Explicitly specify environments in every config file (those settings cascade which means we've been assuming a Node.js environment where we shouldn't have).
2016-11-02 23:51:34 +00:00
// Too many errors
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"max-len": "off",
"brace-style": "off",
"key-spacing": "off",
"camelcase": "off",
Build: Enable ESLint one-var rule for var declarations in browser code Node.js code is written more & more commonly in ES6+ so it doesn't make sense to enable it there. There are many violations in test code so it's disabled there as well. Closes gh-4615 (cherry picked from commit 4a7fc8544e2020c75047456d11979e4e3a517fdf)
2020-03-02 21:25:35 +00:00
"one-var": "off",
Build: ESLint setup improvements 1. Use the short name of the preset in the config. 2. Run ESLint first on non-minified files. 3. Explicitly specify environments in every config file (those settings cascade which means we've been assuming a Node.js environment where we shouldn't have).
2016-11-02 23:51:34 +00:00
"strict": "off",
Build: Switch from jscs+jshint to eslint
2016-05-10 09:06:37 +00:00
Build: ESLint setup improvements 1. Use the short name of the preset in the config. 2. Run ESLint first on non-minified files. 3. Explicitly specify environments in every config file (those settings cascade which means we've been assuming a Node.js environment where we shouldn't have).
2016-11-02 23:51:34 +00:00
// Not really too many - waiting for autofix features for these rules
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"lines-around-comment": "off",
"dot-notation": "off"
Build: Update jsdom; migrate a test with Symbol polyfill to an iframe test So far, we've been testing that jQuery element iteration works with polyfilled Symbol & transpiled for-of via a Node test with jsdom with the Symbol global removed. Unfortunately, jsdom now requires Symbol to be present for its internal functionality so such a test is no longer possible. Instead, it's been migrated to an iframe test with transpiled JavaScript. This PR also enables us to use ECMAScript 2017 or newer in Node.js code. Closes gh-4305
2019-03-04 17:30:51 +00:00
},
"overrides": [
Build: Migrate middleware-mockserver to modern JS The `test/middleware-mockserver.js` file used to have the same ESLint settings applied as other test files that are directly run in tested browsers. Now it shares settings of other Node.js files. The file is now also written using modern JS, leveraging ES2018. Closes gh-5196 (cherry picked from commit ce90a48450ba40586a6567235abb8fd2df84da97)
2023-01-23 22:20:08 +00:00
{
"files": [
"middleware-mockserver.js"
],
"extends": "../.eslintrc-node.json"
},
Build: Update jsdom; migrate a test with Symbol polyfill to an iframe test So far, we've been testing that jQuery element iteration works with polyfilled Symbol & transpiled for-of via a Node test with jsdom with the Symbol global removed. Unfortunately, jsdom now requires Symbol to be present for its internal functionality so such a test is no longer possible. Instead, it's been migrated to an iframe test with transpiled JavaScript. This PR also enables us to use ECMAScript 2017 or newer in Node.js code. Closes gh-4305
2019-03-04 17:30:51 +00:00
{
Build: Run the basic test suite in jsdom The basic test suite is now run in jsdom on all supported Node.js versions (8, 10 & 11 as of now). Closes gh-4310
2019-03-11 19:03:54 +00:00
"files": [
"data/core/jquery-iterability-transpiled-es6.js",
"data/testinit-jsdom.js"
],
Build: Update jsdom; migrate a test with Symbol polyfill to an iframe test So far, we've been testing that jQuery element iteration works with polyfilled Symbol & transpiled for-of via a Node test with jsdom with the Symbol global removed. Unfortunately, jsdom now requires Symbol to be present for its internal functionality so such a test is no longer possible. Instead, it's been migrated to an iframe test with transpiled JavaScript. This PR also enables us to use ECMAScript 2017 or newer in Node.js code. Closes gh-4305
2019-03-04 17:30:51 +00:00
"parserOptions": {
"ecmaVersion": 2015
}
}
]
Build: Switch from jscs+jshint to eslint
2016-05-10 09:06:37 +00:00
}
Reference in New Issue Copy Permalink