Skip to content

fix: prevent nested expansion panels from registering to the same accordion #11342

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
merged 1 commit into from
May 24, 2018

Conversation

josephperrott
Copy link
Member

Fixes #11242

@josephperrott josephperrott added the target: patch This PR is targeted for the next patch release label May 15, 2018
@josephperrott josephperrott requested a review from crisbeto May 15, 2018 17:01
@josephperrott josephperrott requested a review from jelbourn as a code owner May 15, 2018 17:01
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 15, 2018
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

class NestedItems {
@ViewChild('outerItem') outerItem: CdkAccordionItem;
@ViewChild('innerItem') innerItem: CdkAccordionItem;
}
Copy link
Member

Choose a reason for hiding this comment

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

Needs a new line at the end of the file.

providers: [
// Provide CdkAccordion as undefined to prevent nested accordion items from registering
// to the same accordion.
{provide: CdkAccordion, useValue: undefined},
Copy link
Member

Choose a reason for hiding this comment

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

TIL that you can do this. I had to do something similar on the menu, but I ended up adding a provider and having the items register themselves with it.

@crisbeto crisbeto added pr: lgtm action: merge The PR is ready for merge by the caretaker labels May 15, 2018
@ngbot
Copy link

ngbot bot commented May 15, 2018

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure status "continuous-integration/travis-ci/pr" is failing

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@crisbeto crisbeto removed the action: merge The PR is ready for merge by the caretaker label May 15, 2018
@crisbeto
Copy link
Member

@josephperrott seems like there are some lint warnings.

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 the action: merge The PR is ready for merge by the caretaker label May 15, 2018
@mmalerba mmalerba merged commit 9bf720a into angular:master May 24, 2018
@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 9, 2019
@josephperrott josephperrott deleted the expansion-panel branch March 20, 2020 22:10
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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mat-Expansion-Panel in a Mat-Expansion-Panel closes parent on open.
5 participants