Improve documentation for supplying valid escape/sanitize functions about eslint-plugin-no-unsanitized

[rszczypka]

This works but only when done this way

"rules": {
"no-unsanitized/method": ["error", { "escape": { "methods": ["this.domSanitizer.sanitize"] } }],
"no-unsanitized/property": ["error", { "escape": { "methods": ["this.domSanitizer.sanitize"] } }],
}

[mozfreddyb]

We allow custom sanitizers through configurations.
See this testcase to check that users can allow DOMPurify:

eslint-plugin-no-unsanitized/tests/rules/property.js

Lines 154 to 164 in d50ae4d

	{ // issue 108: adding tests for custom escaper
	code: "w.innerHTML = DOMPurify.sanitize('<em>${evil}</em>');",
	parserOptions: { ecmaVersion: 6 },
	options: [
	{
	escape: {
	methods: ["DOMPurify.sanitize"]
	}
	}
	]
	},

(Added in #108).

Does that not work for you?

[Abdullilah]

@mozfreddyb Thanks for your comment.

Could you please tell me how to add it exactly to the configuration?

I tried to add this line to the eslint rules:

"extends": ["plugin:no-unsanitized/DOM"],
"rules": {"no-unsanitized/method": ["error", { "escape": { "methods": ["DomSanitizer.sanitize"] } }]}

OR

"extends": ["plugin:no-unsanitized/DOM"],
"rules": {"no-unsanitized/method": ["error", { "escape": { "methods": ["DOMPurify.sanitize"] } }]}

but I am still getting the same eslint error:

[mozfreddyb]

In your example, you're modifying the options of the no-unsanitized/method, which protects you from calling methods (e.g., insertAdjacentHTML(), document.write(), ..).

You also need to do this for the no-unsanitized/property rule which protects properties (e.g., .innerHTML)

[mozfreddyb]

@Abdullilah Did you end up resolving your issue? I'm leaning towards closing this issue.

[mozfreddyb]

Looks like everything works as intended here. We can repurpose the issue, if someone wants to update the documentation though.