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 Packages Projects Releases Wiki Activity
a75d6b52fa
jquery/test/.eslintrc.json

90 lines
1.6 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,
Core:Manipulation: Add basic TrustedHTML support This ensures HTML wrapped in TrustedHTML can be used as an input to jQuery manipulation methods in a way that doesn't violate the `require-trusted-types-for` Content Security Policy directive. This commit builds on previous work needed for trusted types support, including gh-4642 and gh-4724. One restriction is that while any TrustedHTML wrapper should work as input for jQuery methods like `.html()` or `.append()`, for passing directly to the `jQuery` factory the string must start with `<` and end with `>`; no trailing or leading whitespaces are allowed. This is necessary as we cannot parse out a part of the input for further construction; that would violate the CSP rule - and that's what's done to HTML input not matching these constraints. No trusted types API is used explicitly in source; the majority of the work is ensuring we don't pass the input converted to string to APIs that would eventually assign it to `innerHTML`. This extra cautiousness is caused by the API being Blink-only, at least for now. The ban on passing strings to `innerHTML` means support tests relying on such assignments are impossible. We don't currently have such tests on the `main` branch but we used to have many of them in the 3.x & older lines. If there's a need to re-add such a test, we'll need an escape hatch to skip them for apps needing CSP-enforced TrustedHTML. See https://web.dev/trusted-types/ for more information about TrustedHTML. Fixes gh-4409 Closes gh-4927 Ref gh-4642 Ref gh-4724
2021-09-30 14:00:24 +00:00
"trustedTypes": false,
Build: ESLint details Use eslint pragmas, fix new errors, etc Closes gh-3148
2016-05-10 09:12:28 +00:00
"QUnit": false,
"ajaxTest": false,
"testIframe": false,
"createDashboardXML": false,
Selector: Port Sizzle tests to jQuery Apart from porting most Sizzle tests to jQuery (mostly to its selector module), this commit fixes selector-native so that a jQuery custom compilation that excludes Sizzle passes all tests as well. Closes gh-4406
2019-06-26 19:39:10 +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 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. Fixes gh-5069 Closes gh-5046
2022-06-28 10:39:01 +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
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
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
}
Core: Migrate from AMD to ES modules 🎉 Migrate all source AMD modules to ECMAScript modules. The final bundle is compiled by a custom build process that uses Rollup under the hood. Test files themselves are still loaded via RequireJS as that has to work in IE 11. Tests can now be run in "Load as modules" mode which replaces the previous "Load with AMD" option. That option of running tests doesn't work in IE and Edge as it requires support for dynamic imports. Some of the changes required by the migration: * check `typeof` of `noGlobal` instead of using the variable directly as it's not available when modules are used * change the nonce module to be an object as ECMASscript module exports are immutable * remove some unused exports * import `./core/parseHTML.js` directly in `jquery.js` so that it's not being cut out when the `ajax` module is excluded in a custom compilation Closes gh-4541
2019-11-18 20:15:03 +00:00
},
{
"files": [
"jquery.js",
"data/testinit.js"
],
"parserOptions": {
"ecmaVersion": 2020
}
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: Switch from jscs+jshint to eslint
2016-05-10 09:06:37 +00:00
}
Reference in New Issue Copy Permalink