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(dialog,bottom-sheet): don't provide directionality if no direction is set #11285

Merged
merged 1 commit into from
May 15, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented May 11, 2018

  • Currently the dialog and bottom sheet always provide the Directionality in order to allow for any components placed inside of them to pick up their direction. This is problematic if the consumer didn't set a direction, because the value of the provided Directionality will be set to undefined. These changes switch to only providing the direction if it is defined in the config, otherwise the components will fall back to the global Directionality.
  • Flips around some logic in the drawer so an undefined direction is considered ltr, rather than rtl.

Fixes #11262.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 11, 2018
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release and removed pr: needs review labels May 11, 2018
@ngbot
Copy link

ngbot bot commented May 11, 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.

@ngbot
Copy link

ngbot bot commented May 11, 2018

Hi @crisbeto! This PR has merge conflicts due to recent upstream merges.
Please help to unblock it by resolving these conflicts. Thanks!

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, just needs rebase

@jelbourn jelbourn added pr: needs rebase and removed action: merge The PR is ready for merge by the caretaker labels May 11, 2018
…n is set

* Currently the dialog and bottom sheet always provide the `Directionality` in order to allow for any components placed inside of them to pick up their direction. This is problematic if the consumer didn't set a direction, because the `value` of the provided `Directionality` will be set to `undefined`. These changes switch to only providing the direction if it is defined in the config, otherwise the components will fall back to the global `Directionality`.
* Flips around some logic in the drawer so an undefined direction is consider `ltr`, rather than `rtl`.

Fixes angular#11262.
@crisbeto crisbeto force-pushed the 11262/dialog-undefined-dir branch from ef5bac9 to 01ea799 Compare May 12, 2018 07:48
@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker and removed pr: needs rebase labels May 12, 2018
@ngbot
Copy link

ngbot bot commented May 12, 2018

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

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.

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@tinayuangao tinayuangao merged commit cd37a54 into angular:master May 15, 2018
tinayuangao pushed a commit that referenced this pull request May 15, 2018
…n is set (#11285)

* Currently the dialog and bottom sheet always provide the `Directionality` in order to allow for any components placed inside of them to pick up their direction. This is problematic if the consumer didn't set a direction, because the `value` of the provided `Directionality` will be set to `undefined`. These changes switch to only providing the direction if it is defined in the config, otherwise the components will fall back to the global `Directionality`.
* Flips around some logic in the drawer so an undefined direction is consider `ltr`, rather than `rtl`.

Fixes #11262.
@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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(sidenav): margins are reversed when contained in a dialog
6 participants