feat: add restrictedNamedExportsPattern to no-restricted-exports

[akulsr0]

…ed-exports`

Prerequisites checklist

• I have read the contributing guidelines.

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

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[x] 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)

Made changes to add support for #18360

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

I feel there should be alot more test cases which needs to be added, can add that based on review insights.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: akulsr0 / name: Akul Srivastava (965754e, 0e66cc8, 43f0a46, 9e06882, aa547b9, ac7356f, c881975, 2c4163f, 2984afd)

[netlify]

✅ Deploy Preview for docs-eslint canceled.

Name	Link
🔨 Latest commit	9e06882
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/664210554f28130008b5497c

[Tanujkanti4441]

Hi @akulsr0, thanks for the PR, but the accepted proposal was to add a new option name restrictedNamedExportsPattern that will be a string containing regex pattern to specify the exports to restrict. Can you do the same?

[akulsr0]

Hi @Tanujkanti4441, it seems having restrictedNamedExportsPattern and restrictedNamedExports both would be repetitive. Since, we can do check for regular strings and string patterns with one single option, added that way.

[Tanujkanti4441]

Hi @Tanujkanti4441, it seems having restrictedNamedExportsPattern and restrictedNamedExports both would be repetitive. Since, we can do check for regular strings and string patterns with one single option, added that way.

since something like this is already done in no-restricted-imports rule so i think it's fine to have both the options.

[nzakas]

Please be sure to update the documentation as well.

[mdjermanovic]

Looks good, just we didn't discuss how this option would correlate with restrictDefaultExports. For example, when the pattern matches "default" but some default exports are explicitly allowed by restrictDefaultExports.

I think the best solution is that this option simply doesn't apply to default exports.

[mdjermanovic]

A few more tests to confirm that this option doesn't apply to default.

[mdjermanovic]

LGTM, thanks! Leaving open for @Tanujkanti4441 to verify.

[Tanujkanti4441]

LGTM, thanks for contributing!