uBlock/.jshintrc

{
	"browser": true,
	"devel": true,
	"eqeqeq": true,
	"esversion": 11,
	"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,`
Refactor scriptlets injection code Builtin scriptlets are no longer parsed as text-based resources, they are imported as JS functions, and `toString()` is used to obtain text-based representation of a scriptlet. Scriptlet parameters are now passed as function call arguments rather than by replacing text-based occurrences of `{{i}}`. The arguments are always string values (see below for exception). Support for argument as Object has been added. This opens the door to have scriptlets using named arguments rather than positional arguments, and hence easier to extend functionality of existing scriptlets. Example: example.com##+js(scriplet, { "prop": "adblock", "value": false, "log": true }) Compatibility with user-provided scriptlets has been preserved. User-provided scriptlets can benefit some of the changes: Use the form `function(..){..}` instead of `(function(..){..})();` in order to received scriptlet arguments as part of function call -- instead of using `{{i}}`. If using the form `function(..){..}`, you can choose to receive an Object as argument -- just be sure that your scriptlet's parameter is valid JSON notation. 2023-03-24 19:05:18 +01:00			`"esversion": 11,`
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			`}`