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

fix(bazel): correct regexp test for self-references in metadata #29346

Closed
wants to merge 1 commit into from

Conversation

alexeagle
Copy link
Contributor

Add a test that catches the mistake, should have had this in the previous change

Add a test that catches the mistake, should have had this in the previous change
@alexeagle alexeagle requested a review from mgechev March 15, 2019 22:41
@alexeagle alexeagle requested a review from a team as a code owner March 15, 2019 22:41
@alexeagle alexeagle added target: major This PR is targeted for the next major release action: merge The PR is ready for merge by the caretaker labels Mar 15, 2019
@@ -415,7 +415,7 @@ export * from '${srcDirRelative(inputPath, typingsFile.replace(/\.d\.tsx?$/, '')
if (metadata.exports) {
// Strip re-exports which are now self-references
metadata.exports =
metadata.exports.filter((e: {from: string}) => !relativePathRegex.test(e.from));
metadata.exports.filter((e: {from: string}) => !e.from.match(relativePathRegex));
Copy link
Member

Choose a reason for hiding this comment

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

Might be worth adding a comment here, because .test() seems like the right thing to do and is easy to miss the implications of the g flag.

@jasonaden jasonaden closed this in 9d090cb Mar 18, 2019
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
…lar#29346)

Add a test that catches the mistake, should have had this in the previous change

PR Close angular#29346
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants