item-start and item-end make more sense for RTL
* refactor(item): replaced item-left with item-start
replaced item-right with item-end
* style(item): fix spacing
* fix(item): add backwards support for left/right in ng-content
* fix(item): deprecated old variables, not breaking change
* fix(scss): fix variable name
* fix(item): old attributes deprecated support
* chore(build): WIP getting ionic working with app-scripts
the tsconfig file change is just for testing, this will need to be
undone
* chore(demos): update tsconfig and gitignore for demos
update tsconfig and gitinogre for demos
* chore(build): WIP check in progress with building with app-scripts
this only works with demos/action-sheet currently
* refactor(demos): add custom copy config
add custom copy config
* chore(tsconfig): revert root tsconfig
* chore(demos): change import paths
* chore(demos): move sass config, add new tsconfig, update template
* chore(scripts): update demos tasks to use app scripts with folder name
tweak the createTempTsConfig function to include a path to read from,
move getFolderInfo into util to share
at this point you should be able to run `gulp demos.prod` with a folder
e.g. `--f=alert` and open the index of that test to see it. Doesn’t
work yet with all of the tests at once. Need to have ran `gulp
release.prepareReleasePackage` first.
* chore(build): WIP working on getting all of the demos building
* chore(demos): update demos task for app-scripts build
* chore(demos): fix tslint errors thrown by app-scripts
* chore(demos): get the demos working with fonts and variable file
* chore(demos): add watch task to the new prod task
* chore(demos): remove old demos.prod file and rename new one to it
* chore(npm): remove build npm script
* chore(demos): only log component name in url if one was passed
* chore(demos): WIP refactor gulp demos task to use SystemJS
move build files into dist/demos and comment out the AoT demos task for
right now. This makes both `gulp demos` and `gulp demos.watch`work
again.
references #8411
* docs(demos): fix infinite scroll demo
* chore(demos): move old demos task to demos.prod
update the demos file with shared tasks, include the shared css
* docs(demos): fix API demos to use correct styles
* chore(demos): remove the main.ts files from each demo
* chore(demos): add prod template and constant
* chore(demos): remove tsconfig and package from demos
* chore(demos): update app.module path to ionic
* chore(demos): update app.module path to ionic
* chore(demos): update prod task for demos to work with AoT
also puts the demo build files into dist/ instead of the src directory
* docs(demos): update deploy and docs tasks for new build
* docs(scripts): update demos README
* chore(demos): fix path for prod build
BREAKING CHANGES:
Colors should be passed in the `color` input on components, not added
individually as an attribute on the component.
For example:
```
<ion-tabs primary>
```
Becomes
```
<ion-tabs color=”primary”>
```
Or to bind an expression to color:
```
<ion-navbar [color]="barColor">
...
</ion-navbar>
```
```ts
@Component({
templateUrl: 'build/pages/about/about.html'
})
export class AboutPage {
barColor: string;
constructor(private nav: NavController, platform: Platform) {
this.barColor = platform.is('android') ? 'primary' : 'light';
}
}
```
Reason for this change:
It was difficult to dynamically add colors to components, especially if
the name of the color attribute was unknown in the template.
This change keeps the css flat since we aren’t chaining color
attributes on components and instead we assign a class to the component
which includes the color’s name.
This allows you to easily toggle a component between multiple colors.
Speeds up performance because we are no longer reading through all of
the attributes to grab the color ones.
references #7467closes#7087closes#7401closes#7523
BREAKING CHANGES:
- `<button>` becomes `<button ion-button>`
- `<a button>` becomes `<a ion-button>`
- `<button ion-item>` does not get the `ion-button` attribute
- Buttons inside of `<ion-item-options>` do get the `ion-button`
attribute
- Removed the `category` attribute, this should be passed in
`ion-button` instead.
- Button attributes added for icons in buttons: `icon-only`,
`icon-left`, and `icon-right`
closes#7466
BREAKING CHANGES:
The Option component’s `checked` attribute has been renamed to
`selected` in order to select an option. This is to the follow the MDN
spec for a select option:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/option
If a `ngModel` is added to the Select component the value of the
`ngModel` will take precedence over the `selected` attribute.
references #7334