uBlock/.jshintrc

{
	"browser": true,
	"devel": true,
	"eqeqeq": true,
	"esversion": 9,
	"globals": {
		"chrome": false,     // global variable in Chromium, Chrome, Opera
		"globalThis": false,
		"self": false,
		"vAPI": false,
		"URLSearchParams": false,
		"WebAssembly": false
	},
	"laxbreak": true,
	"newcap": false,
	"nonew": false,
	"strict": "global",
	"sub": true,
	"undef": true,
	"unused": true,
	"validthis": true
}
Add .jshintrc, and use the "use strict" directive .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file. 2014-10-19 13:11:27 +02:00			`{`
			`"browser": true,`
			`"devel": true,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"eqeqeq": true,`
Rewrite static filtering parser This commit is a rewrite of the static filtering parser into a tree-based data structure, for easier maintenance and better abstraction of parsed filters. This simplifies greatly syntax coloring of filters and also simplify extending filter syntax. The minimum version of Chromium-based browsers has been raised to version 73 because of usage of String.matchAll(). 2023-01-23 22:53:18 +01:00			`"esversion": 9,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"globals": {`
fix #2925 2017-08-30 00:32:00 +02:00			`"chrome": false, // global variable in Chromium, Chrome, Opera`
Add option to filter by HTTP method in static network filters Related issue: - https://github.com/uBlockOrigin/uBlock-issues/issues/2117 Option: `method=` Value: a list of `\|`-separated lowercased method names. Negated method names are allowed. These are valid methods: - connect - delete - get - head - options - patch - post - put As per DNR's own documentation: - https://developer.chrome.com/docs/extensions/reference/declarativeNetRequest/#type-RequestMethod The logger shows the method used for every network request. It's possible to filter the logger output for most-common methods: `get`, `head`, `post`. 2022-12-18 21:36:59 +01:00			`"globalThis": false,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"self": false,`
			`"vAPI": false,`
Remove globals usage from hntrie.js (#3842) 2021-08-21 13:33:53 +02:00			`"URLSearchParams": false,`
			`"WebAssembly": false`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`},`
			`"laxbreak": true,`
			`"newcap": false,`
Add .jshintrc, and use the "use strict" directive .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file. 2014-10-19 13:11:27 +02:00			`"nonew": false,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"strict": "global",`
Add .jshintrc, and use the "use strict" directive .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file. 2014-10-19 13:11:27 +02:00			`"sub": true,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"undef": true,`
			`"unused": true,`
adjust jshint behavior 2017-12-05 14:38:50 +01:00			`"validthis": true`
#608: this fixes a bunch of strictness-related warnings 2015-08-18 17:44:24 +02:00			`}`