Skip to content

fix(datepicker): producing wrong selector for disabled dates for themes inside a selector #10904

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
Apr 19, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Apr 18, 2018

Fixes the selector for the disabled dates inside the calendar being wrong, if the theme is scoped under a selector, e.g.

.dark-theme {
  @include angular-material-theme($dark-theme);
}

Relates to #10889.

For reference:
screenshot at apr 18 06-44-29

…es inside a selector

Fixes selector for the disabled dates inside the calendar being wrong, if the theme is scoped under a selector, e.g.

```scss
.dark-theme {
  @include angular-material-theme($dark-theme);
}
```

Relates to angular#10889.
@crisbeto crisbeto requested a review from mmalerba as a code owner April 18, 2018 12:47
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 18, 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 Apr 18, 2018
@mmalerba mmalerba merged commit 54301da into angular:master Apr 19, 2018
crisbeto added a commit to crisbeto/material2 that referenced this pull request Apr 22, 2018
Replaces the `selector-nested-pattern-scoped` Stylelint rule with a new rule called `no-ampersand-beyond-selector-start`. The new rule will enforce that ampersands can only be used at the start of selectors in theme mixins. This will catch issues like angular#10889 and angular#10904 where having an ampersand anywhere else in the selector will work in most cases, but will break down once the mixin is wrapped in a selector.
andrewseguin pushed a commit that referenced this pull request Apr 26, 2018
…10949)

Replaces the `selector-nested-pattern-scoped` Stylelint rule with a new rule called `no-ampersand-beyond-selector-start`. The new rule will enforce that ampersands can only be used at the start of selectors in theme mixins. This will catch issues like #10889 and #10904 where having an ampersand anywhere else in the selector will work in most cases, but will break down once the mixin is wrapped in a selector.
@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.

3 participants