Skip to content

Latest commit

 

History

History
158 lines (103 loc) · 5.24 KB

CONTRIBUTING.md

File metadata and controls

158 lines (103 loc) · 5.24 KB

Contributing

Contributions are always welcome, no matter how large or small!

We want this community to be friendly and respectful to each other. Please follow it in all your interactions with the project. Before contributing, please read the code of conduct.

Development workflow

This project is a monorepo managed using Yarn workspaces. It contains the following packages:

  • The core library package in the packages directory
  • React Native example app in apps/example
  • Expo example app in apps/example-expo

To get started with the project, run yarn in the root directory to install the required dependencies for each package:

yarn

Since the project relies on Yarn workspaces, you cannot use npm for development.

The example apps in the apps directory demonstrate usage of the library. You need to run one of them to test any changes you make.

They are configured to use the local version of the library, so any changes you make to the library's source code will be reflected in the example apps. Changes to the library's JavaScript code will be reflected without a rebuild, but native code changes will require a rebuild of the example app.

If you want to use Android Studio or XCode to edit the native code, you can open the apps/example/android or apps/example/ios directories respectively in those editors.

You can use various commands from the root directory to work with the project.

To start the packager for the React Native example:

yarn workspace react-native-bottom-tabs-example start

To run the React Native example app on Android:

yarn workspace react-native-bottom-tabs-example android

To run the React Native example app on iOS:

Make sure to install cocoapods-swift-modular-headers gem, otherwise pod install will fail.

gem install cocoapods-swift-modular-headers

Next you can install cocoapods.

cd apps/example/ios
pod install
cd -
yarn ios

To run the Expo example:

yarn workspace example-expo start

By default, the example is configured to build with the new architecture. To run the example with the old architecture, you can do the following:

  1. For Android, run:

    cd apps/example
ORG_GRADLE_PROJECT_newArchEnabled=false yarn android

  2. For iOS, run:

    cd apps/example/ios
RCT_NEW_ARCH_ENABLED=0 pod install
cd -
yarn example ios

If you are building for a different architecture than your previous build, make sure to remove the build folders first. You can run the following command to cleanup all build folders:

yarn clean

To confirm that the app is running with the new architecture, you can check the Metro logs for a message like this:

Running "ReactNativeBottomTabsExample" with {"fabric":true,"initialProps":{"concurrentRoot":true},"rootTag":1}

Note the "fabric":true and "concurrentRoot":true properties.

Make sure your code passes TypeScript and ESLint. Run the following to verify:

yarn typecheck
yarn lint

To fix formatting errors, run the following:

yarn lint --fix

Remember to add tests for your change if possible. Run the unit tests by:

yarn test

Commit message convention

We follow the conventional commits specification for our commit messages:

  • fix: bug fixes, e.g. fix crash due to deprecated method.
  • feat: new features, e.g. add new method to the module.
  • refactor: code refactor, e.g. migrate from class components to hooks.
  • docs: changes into documentation, e.g. add usage example for the module..
  • test: adding or updating tests, e.g. add integration tests using detox.
  • chore: tooling changes, e.g. change CI config.

Our pre-commit hooks verify that your commit message matches this format when committing.

Linting and tests

ESLint, Prettier, TypeScript

We use TypeScript for type checking, ESLint with Prettier for linting and formatting the code, and Jest for testing.

Our pre-commit hooks verify that the linter and tests pass when committing.

Publishing to npm

We use changesets to make it easier to publish new versions. It handles common tasks like bumping version based on semver, creating tags and releases etc.

To publish new versions, run the following:

yarn publish-packages

Sending a pull request

Working on your first pull request? You can learn how from this free series: How to Contribute to an Open Source Project on GitHub.

When you're sending a pull request:

  • Prefer small pull requests focused on one change.
  • Verify that linters and tests are passing.
  • Review the documentation to make sure it looks good.
  • Follow the pull request template when opening a pull request.
  • For pull requests that change the API or implementation, discuss with maintainers first by opening an issue.