docs: Update configuration file pages

[bpmutter]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Clean up page copy and add small introductions on pages Configuration Files and Configuration Files (New)

Notes:

• Updated many verbs to be present tense from future tense. this is a general technical writing practice. See Microsoft style guide for more information.
• Some changes across the 2 pages are fairly duplicative (since pages similar)
• Noticed needed more docs for shared settings while working on this. Created separate issue for that - Docs: Better example for shared setting #16507

Is there anything you'd like reviewers to focus on?

Part of fix for #16473
Resolves #16478

[netlify]

✅ Deploy Preview for docs-eslint ready!

Name	Link
🔨 Latest commit	a5e1b9c
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/637e71580d14ed0009d13bd3
😎 Deploy Preview	https://deploy-preview-16509--docs-eslint.netlify.app/user-guide/configuring/configuration-files-new
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[snitin315]

Suggested change

ESLint supports adding shared settings into configuration files. Plugins use `settings` to specify information that should be shared across all of its rules. When you add a `settings` object to a configuration object, and it is supplied to every rule executed by that configuration object. This may be useful if you are adding custom rules and want them to have access to the same information. Here's an example:

ESLint supports adding shared settings into configuration files. Plugins use `settings` to specify the information that should be shared across all of its rules. When you add a `settings` object to a configuration object, and it is supplied to every rule executed by that configuration object. This may be useful if you are adding custom rules and want them to have access to the same information. Here's an example:

[bpmutter]

this change looks good.

but upon re-reading the sentence, i think there's something wrong with the 'across all its rules' phrase. what does 'its' refer to?

@snitin315 or @nzakas, do you know?

[snitin315]

I believe it is referring to the Plugin here.

[nzakas]

That’s correct. Note: settings are not limited to one plugin. Every plugin receives every setting that was set in the config. It’s a convention that plugins namespace the settings they are interested in to avoid collisions with others.

[bpmutter]

thanks for the clarifications. i believe i've addressed this confusion in the latest commit, 53dd21d.

also added the word 'the' before information that started this conversation.

[bpmutter]

applied suggestions from code review. 1 outstanding question.

[bpmutter]

addressed outstanding question. ready for re-review

[snitin315]

Lint is failing, can you check?

[mdjermanovic]

Lint is failing, can you check?

Will be fixed by #16564

[mdjermanovic]

"it is supplied to every rule executed by that configuration object" might be misleading. It sounds like the settings object is only supplied to rules: {} from the same configuration object.

[bpmutter]

@mdjermanovic
what'd be correct, it's applied to all rules in the project?

[nzakas]

I think you can just drop “executed by that configuration object”.

[mdjermanovic]

It's supplied to every rule when linting a file to which the configuration object applies, but those rules don't have to be enabled by that configuration object.

For example:

module.exports = [
    {
        rules: {
            "my-plugin/my-rule": "error"
        }
    },
    {
        files: ["a.js"],
        settings: {
            data: "something"
        }
    }
];

When linting a.js, my-plugin/my-rule will be supplied with { data: "something" } (as context.settings), although my-plugin/my-rule rule isn't enabled in the same configuration object where settings are defined.

Since this sentence only briefly describes what settings means, it could just say "it is supplied to every rule", as @nzakas suggested.

[bpmutter]

thanks for the further clarification, implementing nicholas's suggestion!

[nzakas]

LGTM. Just waiting for @mdjermanovic to review.

[mdjermanovic]

LGTM, thanks!