Skip to content

Files

Latest commit

e946f7e · Dec 16, 2020

History

History

scripts

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Jul 9, 2020
Nov 20, 2018
Aug 11, 2020
Aug 20, 2018
Dec 19, 2019
Nov 12, 2018
Dec 11, 2017
Dec 26, 2019
Sep 11, 2018
Oct 19, 2018
May 1, 2018
Jun 26, 2017
Aug 22, 2018
Apr 27, 2018
Aug 11, 2017
Dec 11, 2017
Dec 14, 2016
Dec 11, 2017
Jan 25, 2017
Aug 8, 2016
Mar 31, 2020
Mar 1, 2019
Apr 22, 2019
Jan 6, 2017
Aug 7, 2017
Aug 11, 2017
Dec 11, 2017
Dec 11, 2017
Nov 16, 2017
Dec 11, 2017
Dec 16, 2020
Sep 25, 2019
Dec 11, 2017
Dec 5, 2018
Dec 22, 2017

README.md

Scripts

Scripts for maintaining Material Components for iOS—none of these scripts are required to use MDC or for casual contributors.

The important scripts are:

  • prep_all: prepare the Material Components catalog, tests, and demos apps for building.
  • build_all: build the Material Components catalog and each of our demo apps.
  • test_all: build and test the Material Components unit and integration tests.
  • clean_all: remove artifacts from the prep_all, build_all, and test_all scripts.
  • check_components: run component checks for documentation, examples, etc.
  • install_contributor_tools: install local contributor tools to speed up the development cycle.

Languages

Material Components follows Google's language standards for scripting. The following languages can be used for scripts:

Either language can be used for a particular purpose, but larger or more complex scripts should be written in (or converted to) Python. Bash scripts get unwieldy quickly and advanced Bash scripting knowledge is currently less common than advanced Python scripting knowledge.

The intent is that the scripts will run on relatively current OS X machines with (only) Xcode installed.

iOS Codelabs Build Tests

iOS codelabs build tests ensure that the Objective C and Swift versions of Codelab 104 Complete and Codelab 111 Complete can be built. If a release fails the codelabs build tests, follow these steps:

  1. If the release changes a component that the codelabs use, submit a PR to the codelabs repo with the appropriate changes for the adjusted component. Address each codelab and language that is affected by the change (it may be helpful to run ./build_codelabs -a to determine which codelabs are affected).
  2. Merge the PR into the codelabs repo, and then rerun the codelabs build tests.
  3. Continue with the release process.