Skip to content

build: add lint rule to avoid relative cross entry-point imports/exports #17741

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

Merged

Conversation

devversion
Copy link
Member

Adds a new lint rule to avoid relative cross entry-point imports
and exports. If a public entry-point imports from another entry-point
it should use the public module name in order to comply with the
Angular Package format, and to avoid unnecessary code inlining when
creating flat entry-point bundles.

Restructures the cdk testing fake-event code into cdk/testing/testbed
since that is where the fake event code is primarily used. This
makes the new lint rule happy, and also improves the public API
of cdk/testing since interfaces like ElementDimensions are
part of the TestElement class and should therefore be exported.

@devversion devversion added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release labels Nov 18, 2019
@devversion devversion added this to the 9.0.0 milestone Nov 18, 2019
@devversion devversion requested review from jelbourn, mmalerba and a team as code owners November 18, 2019 14:20
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 18, 2019
@devversion
Copy link
Member Author

I'm adding the P1 label since it improves the public API of the new CDK testing harness stuff, and currently we miss public types for ModifierKeys and ElementDimensions.

Also it's generally good before we release final to be sure that we do not have any possibly breaking relative cross entry-point imports/exports.

@devversion devversion force-pushed the refactor/cdk-testing-fake-events branch 3 times, most recently from d68e67c to 183ff02 Compare November 18, 2019 14:30
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 18, 2019
@devversion devversion force-pushed the refactor/cdk-testing-fake-events branch from 183ff02 to 2c13425 Compare November 20, 2019 09:44
Adds a new lint rule to avoid relative cross entry-point imports
and exports. If a public entry-point imports from another entry-point
it should use the public module name in order to comply with the
Angular Package format, and to avoid unnecessary code inlining when
creating flat entry-point bundles.

Restructures the cdk testing fake-event code into `cdk/testing/testbed`
since that is where the fake event code is primarily used. This
makes the new lint rule happy, and also improves the public API
of `cdk/testing` since interfaces like `ElementDimensions` are
part of the `TestElement` class and should therefore be exported.
@devversion devversion force-pushed the refactor/cdk-testing-fake-events branch from 2c13425 to 1b2a168 Compare November 20, 2019 11:33
@jelbourn jelbourn merged commit a8cff1e into angular:master Nov 22, 2019
@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 Dec 23, 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 PR author has agreed to Google's Contributor License Agreement P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants