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(overlay): validate that ConnectedPositionStrategy positions are passed in correctly at runtime #9466

Merged
merged 1 commit into from
Feb 8, 2018

Conversation

crisbeto
Copy link
Member

Since we have some cases where we pass in positions verbatim to the connected position strategy (the connected position directive), we could end up in a situation where the consumer passed in a set of invalid positions that don't break necessarily, but don't work correctly either. These changes add some sanity checks at runtime to make debugging easier.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 18, 2018
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.

I think this will have to be a major version change since it's possible for an app to have an invalid position that by coincidence never gets used

throw Error('ConnectedPositionStrategy: At least one position is required.');
}

this._preferredPositions.forEach(pair => {
Copy link
Member

Choose a reason for hiding this comment

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

Add a TODO to remove this check once Angular's template type checker is good enough to not need it?

@jelbourn jelbourn added the target: major This PR is targeted for the next major release label Jan 19, 2018
…assed in correctly at runtime

Since we have some cases where we pass in positions verbatim to the connected position strategy (the connected position directive), we could end up in a situation where the consumer passed in a set of invalid positions that don't break necessarily, but don't work correctly either. These changes add some sanity checks at runtime to make debugging easier.
@crisbeto
Copy link
Member Author

Addressed the feedback @jelbourn.

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, will hold off merging until we switch master over to being 6.0

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jan 19, 2018
@mmalerba mmalerba merged commit 6a8ce02 into angular:master Feb 8, 2018
tinayuangao pushed a commit that referenced this pull request Feb 9, 2018
…assed in correctly at runtime (#9466)

Since we have some cases where we pass in positions verbatim to the connected position strategy (the connected position directive), we could end up in a situation where the consumer passed in a set of invalid positions that don't break necessarily, but don't work correctly either. These changes add some sanity checks at runtime to make debugging easier.
@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 8, 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 target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants