Skip to content

Conversation

brandyscarney
Copy link
Member

@brandyscarney brandyscarney commented Sep 16, 2019

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Build (npm run build) was run locally and any changes were pushed
  • Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

Issue Number: fixes #18285

In order to set the mode for child components you have to set it on each child:

<ion-segment mode="md">
  <ion-segment-button mode="md">
     This is MD
  </ion-segment>
  <ion-segment-button mode="md">
     This is MD
  </ion-segment>
  <ion-segment-button mode="md">
     This is MD
  </ion-segment>
</ion-segment>

What is the new behavior?

  • Allows you to set the mode on a parent and have it inherited by children
<ion-segment mode="md">
  <ion-segment-button>
     This is MD
  </ion-segment>
  <ion-segment-button>
     This is MD
  </ion-segment>
  <ion-segment-button>
     This is MD
  </ion-segment>
</ion-segment>

Does this introduce a breaking change?

  • Yes
  • No

This is considered breaking since users may not be expecting it but I think it is an improvement overall.

Other information

@liamdebeasi
Copy link
Contributor

One small thing I noticed:

image

The fill for the ios button is gone when doing Mode: segment md, button ios. Is this intentional? If so, I imagine the fill is dependent on the mode of the parent segment?

@brandyscarney
Copy link
Member Author

@liamdebeasi Yes, because ios and md styles are so different if you switch the mode on the button it will look broken without extra styling, but it is adding the proper mode so it is working correctly in that aspect. Segment sets the variables for the segment-button in the segment component.

BREAKING CHANGES

Removes ion-nav-pop, ion-nav-push and ion-nav-set-root in favor of using ion-nav-link with router-direction
brandyscarney and others added 11 commits September 27, 2019 17:01
BREAKING CHANGES

Removes `scss` files from the distributed files. Please use CSS variables for theming instead.
BREAKING CHANGES

The Ionic default colors have been updated to the following:

primary:         #3880ff
secondary:       #3dc2ff
tertiary:        #5260ff
success:         #2dd36f
warning:         #ffc409
danger:          #eb445a
light:           #f4f5f8
medium:          #92949c
dark:            #222428

`primary`, `light` and `dark` have not changed. The contrast color for `warning` has been updated to `#000`.
BREAKING CHANGES

Removes all CSS utility attributes. Please use CSS classes instead. See the documentation for the correct class names: https://ionicframework.com/docs/layout/css-utilities
BREAKING CHANGES

Skeleton text's `width` property has been removed. Please use CSS instead to set the width.
BREAKING CHANGES

The deprecated `ion-anchor` component has been removed in favor using `ion-router-link`. It should still only be used with vanilla and Stencil JavaScript projects. For Angular projects, use an `<a>` and `routerLink` with the Angular router.
)

BREAKING CHANGES

The `show-cancel-button` property of the searchbar no longer accepts boolean values. Accepted values are strings: `"focus"`, `"always"`, `"never"`. The following should change:

```
<ion-searchbar show-cancel-button>
<ion-searchbar show-cancel-button="true">
<ion-searchbar show-cancel-button="false">
```

becomes

```
<ion-searchbar show-cancel-button="focus">
<ion-searchbar show-cancel-button="focus">
<ion-searchbar show-cancel-button="never">
```
@brandyscarney
Copy link
Member Author

This is ready to merge when the build passes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants