Skip to content

Latest commit

 

History

History
104 lines (67 loc) · 3.86 KB

CONTRIBUTING.md

File metadata and controls

104 lines (67 loc) · 3.86 KB
Raw

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

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

npm i

While it's possible to use npm, the tooling is built around npm, so you'll have an easier time if you use npm for development.

While developing, you can run the example app to test your changes. Any changes you make in your library's JavaScript code will be reflected in the example app without a rebuild. If you change any native code, then you'll need to rebuild the example app.

To start the packager:

npm run example start

To run the example app on Android:

npm run example android

To run the example app on iOS:

npm run example ios

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

npm run typecheck
npm run lint

To fix formatting errors, run the following:

npm run lint --fix

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

npm run test

To edit the Objective-C or Swift files, open example/ios/ReactNativeCapfaceSdkExample.xcworkspace in XCode and find the source files at Pods > Development Pods > @capitual/react-native-capface-sdk.

To edit the Java or Kotlin files, open example/android in Android studio and find the source files at capitual-react-native-capface-sdk under Android.

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.

Scripts

The package.json file contains various scripts for common tasks:

  • npm run bootstrap: setup project by installing all dependencies and pods.
  • npm run typecheck: type-check files with TypeScript.
  • npm run lint: lint files with ESLint.
  • npm run test: run unit tests with Jest.
  • npm run example start: start the Metro server for the example app.
  • npm run example android: run the example app on Android.
  • npm run example ios: run the example app on iOS.

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.