8 Commits

Author SHA1 Message Date
Jeff Verkoeyen
a1daebd783 Bump the release. 2018-09-07 12:58:22 -04:00
Jeff Verkoeyen
944be857d4 Bump the release. 2018-09-05 09:22:16 -04:00
Jeff Verkoeyen
1d2845b582 Merge branch 'release-candidate' into develop 2018-09-05 08:58:53 -04:00
Cody Weaver
05d4be9e43
[ActionSheet] Add typography themer (#4966)
Add a typography themer to the Action Sheet component.
2018-08-30 19:33:34 -04:00
Yarden Eitan
c959322480 bumped version number to 62.0.0 2018-08-30 18:11:49 -04:00
Cody Weaver
1f4b8e0789
[ActionSheet] Add Action sheet (#4830)
This PR adds the Action Sheet component for the iOS platform. In a later PR theming will be added and then an App Bar to support full screen.
2018-08-28 06:16:23 -04:00
guylivneh
b2d17e1ed6 [NavigationDrawer] Adding the navigation drawer component (#4886)
Adding the navigation drawer component that adds a presentation controller for showing UIViewControllers as a bottom drawer.

History of the component (last CL submitted for it): cl/209765207
Design doc: go/mdc-ios-navigation-drawer

This component will be the first alpha component in this repo, this means that it can still change and will not be included as part of the podspec at first.
2018-08-27 16:00:40 -04:00
featherless
bb194fa168
Introduce an Alpha program for MDC components. (#4892)
The intent of the Alpha program is to provide a place for component code to land that may not be fully ready for production, but for which we still want active collaboration with the team and potentially some early adoption with select clients.

Any new component that we implement will first land in the MaterialComponentsAlpha.podspec as a subspec, similar to how components are defined in the MaterialComponents.podspec.

Alpha components will appear in MDCCatalog and MDCDragons along with all of their examples and unit tests after a `pod install`. From the point of view of our catalogs, these components are just like any other.

From the point of view of the public, Alpha components are not made available as part of our published pod. External clients that wish to use an Alpha component in their app will need to manually clone the repo and add the code to their project. This is by design.

Alpha components are not subject to our deprecation policy and we will not provide behavioral flags for gradual migration of runtime behaviors.

Changes to Alpha components will have **no** effect on our release version numbers.

Once a component is ready for general production use, we will graduate the component to the MaterialComponents.podspec. At this point the component will be subject to all of the processes and expectations that any other production component.
2018-08-24 14:55:42 -04:00