Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Support arbitrary module namespace names in no-restricted-exports #15478

merged 2 commits into from Jan 5, 2022


Copy link

@mdjermanovic mdjermanovic commented Jan 2, 2022

Prerequisites checklist

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:

Refs #15465, fixes no-restricted-exports.

What changes did you make? (Give an overview)

Added a helper function astUtils.getModuleExportName, and updated no-restricted-exports rule to support tha new syntax.

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

@mdjermanovic mdjermanovic added rule accepted feature new syntax labels Jan 2, 2022
@mdjermanovic mdjermanovic merged commit fd3683f into main Jan 5, 2022
14 checks passed
@mdjermanovic mdjermanovic deleted the issue15465-norestrictedexports branch Jan 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
accepted feature new syntax rule
None yet

Successfully merging this pull request may close these issues.

None yet

2 participants