5 Commits

Author	SHA1	Message	Date
dniz	ade4df00cb	Change Gradle build to output single Maven artifact ... PiperOrigin-RevId: 190774454	2018-04-03 11:49:01 -04:00
markwei	2e2c348e6f	Add new enforceMaterialTheme attribute that you can set in any style to denote that the style uses a new attribute that must exist in the app theme. ... Update ThemeEnforcement to read this new attribute, and check for Material theme. Change the ThemeEnforcement API to replace Context#obtainStyledAttributes(). See followup CL for how this attribute is used. PiperOrigin-RevId: 184074635	2018-03-02 15:36:20 -05:00
dniz	7825a4f80f	Fix Chip and MaterialSwitch lint issues ... PiperOrigin-RevId: 181742611	2018-01-12 11:37:02 -05:00
travisc	1ef167edc2	Move ThemeUtils to internal package and rename to ThemeEnforcement. ... This is a first step in reversing the dependency flow around the `theme` package in MDC. In a future commit, I'll make theme contain all the various MaterialComponents theme definitions, and it will thus depend on the various packages containing our components (widget, button, toggle, etc.). The theme package will be empty as of this commit, but since I plan to use it in the next one I've left the build infrastructure in place. PiperOrigin-RevId: 180737806	2018-01-11 11:09:46 -05:00
Material Design Team	1e32cc7443	Rename Toggle & toggle - MaterialSwitch & switch ... We cannot use 'switch' as a package name in java but would like to keep naming conventions inline with sysUi - SwitchCompat. This feels clumsy to me as we now have items such as <android.support.design.materialswitch.MaterialSwitch but I am not sure how else to get around this. PiperOrigin-RevId: 180649420	2018-01-11 11:07:43 -05:00