Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Make export-name RegExp more strict #642

Merged

Conversation

IllusionMH
Copy link
Contributor

@IllusionMH IllusionMH commented Nov 5, 2018

PR checklist

Overview of change:

This PR requires exported class name strictly match start of file name followed by . and atleast 1 more extension character.

Will rebase/cleanup after #641 merged

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

Ignore Rule class name from checks in this repo, because all rule files exports just Rule which is violation.

I think nice to have in 6.0 since it is more strict now and may be breaking for those who uses it from recommended_ruleset.js

@IllusionMH IllusionMH force-pushed the strict-export-name-regexp-632 branch from d014bc5 to 74bb09d Compare November 5, 2018 17:52
tslint.json Show resolved Hide resolved
@IllusionMH IllusionMH force-pushed the strict-export-name-regexp-632 branch from 74bb09d to 00809af Compare November 5, 2018 21:19
Copy link

@JoshuaKGoldberg JoshuaKGoldberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

I would be a bit more nervous if it didn't have the "allow" option.

@JoshuaKGoldberg JoshuaKGoldberg merged commit 2f9fa68 into microsoft:master Nov 5, 2018
@JoshuaKGoldberg JoshuaKGoldberg added this to the 6.0.0-beta0 milestone Nov 6, 2018
@IllusionMH IllusionMH deleted the strict-export-name-regexp-632 branch December 1, 2018 01:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect RegExp in export-name rule leads to superfluously permissive
2 participants