times-components-native Home of The Times’ react native
components used in the mobile and tablet apps.
For more details read the React Native documentation.
brew install fontforge
(See Fonts section)yarn install
cd ios && pod install && cd -
yarn start
and leave it runningIn order to run development servers for native applications, start react-native dev server via:
yarn android:native
or yarn ios:native
For step by step guide, see the corresponding documentation for android and iOS.
There is a mixture of different checks & tests split acrossing linting, typechecking and unit tests.
yarn lint
yarn test:all
yarn test:android
yarn test:ios
yarn test:common
The release to production pipeline comes with a hold step on CircleCI for builds running on the master
branch. Once you bump the version in a PR, merge your PR and trigger the hold_release_prod
step in the build. This will publish the artifacts, for iOS in the artifacts repo and for Android in JFrog.
Similar to the production releases, you can triger builds with the hold_release_beta
step from all branches (apart from master
) as long as the version in package.json
is a beta version (includes the word beta). Once the “hold” step is approved, the pipeline will build and push to the beta artifacts repos (different location to prod).
Once a release is published, you will have to bump the version in the native apps. That would be the Podfile
for iOS
and the build.gradle
file for Android.
In order to view the storybook on native, you’ll need to fix broken fonts. This fix is done automatically when running storybook (both web and native), but requires that fontforge is installed, otherwise the fix won’t be applied and you’ll get the classic red error screen when trying to use a broken font.
See utils package on how to update the schema
See the CONTRIBUTING.md for an extensive breakdown of the project
Author: newsuk
Source Code: https://github.com/newsuk/times-components-native
#react-native #react #mobile-apps