CONTRIBUTING

# Contributing

We want this community to be friendly and respectful to each other. Please follow it in all your interactions with the project.

## Development workflow

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

```sh
yarn
```

While developing, you will have 2 example apps that can be used 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.

### Expo example app

Go to the Expo example app:

```sh
cd examples/expo-example
```

For the first time (and whenever you make a change in native code or in Expo Config Plugin implementation) run:

```sh
yarn expo prebuild --clean
```

To run the example app on Android:

```sh
yarn android
```

To run the example app on iOS:

```sh
yarn ios
```

### Bare RN example app

Go to the bare RN example app

```sh
cd examples/bare-example
```

To install Pods:

```sh
npx pod-install
```

To start the packager:

```sh
yarn start
```

To run the example app on Android:

```sh
yarn android
```

To run the example app on iOS:

```sh
yarn ios
```

### Developing Expo Config Plugin

The codebase of Expo Config Plugin is located in:

- `packages/react-native-legal/plugin`
- `packages/react-native-legal/plugin-utils`
- `packages/react-native-legal/app.plugin.js` (the entry point)

To test the changes, build the plugin run (from the root directory, the one with consisting all workspaces):

```sh
yarn workspace react-native-legal build-plugins
```

and then, run (from the Expo example app's directory):

```sh
yarn expo prebuild --clean
```

### Developing RN CLI plugin

The codebase of RN CLI plugin is located in:

- `packages/react-native-legal/bare-plugin`
- `packages/react-native-legal/plugin-utils`
- `packages/react-native-legal/react-native.config.js` (the entry point)

To test the changes, build the plugin run (from the root directory, the one with consisting all workspaces):

```sh
yarn workspace react-native-legal build-plugins
```

and then just run the plugin (from the bare RN example app's directory):

```sh
yarn react-native legal-generate
```

This will generate/modify several files in native `android` & `ios` projects.
Remember to revert those changes before running the plugin again.

### Before pushing the changes

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

```sh
yarn typescript
yarn lint:js
```

To fix formatting errors, run the following:

```sh
yarn lint:js --fix
```

For Swift code, run the following to verify code quality:

```sh
yarn lint:swift
```

To fix Swift formatting errors, run:

```sh
yarn format:swift
```

Objective-C code is linted and formatted using following commands:

Lint code
```sh
yarn lint:objc
```

Fixing formatting errors
```sh
yarn format:objc
```

For Kotlin codebase, run the following to verify code quality:

Lint Kotlin code
```sh
yarn lint:android
```

Format Kotlin code
```sh
yarn format:android
```

To edit the iOS native part, open `examples/bare-example/ios/ReactNativeLegalBareExample.xcworkspace` in XCode and find the source files at `Pods > Development Pods > ReactNativeLegal`.

To edit the Android native part, open `examples/bare-example/android` in Android studio and find the source files at `react-native-legal` under `Android`.

### Commit message convention

We follow the [conventional commits specification](https://www.conventionalcommits.org/en) 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](https://eslint.org/), [Prettier](https://prettier.io/), [TypeScript](https://www.typescriptlang.org/), [swift-format](https://github.com/swiftlang/swift-format), [clang-format](https://clang.llvm.org/docs/ClangFormat.html), [Spotless](https://github.com/diffplug/spotless), [ktfmt](https://facebook.github.io/ktfmt/)

We use [TypeScript](https://www.typescriptlang.org/) for type checking, [ESLint](https://eslint.org/) with [Prettier](https://prettier.io/) for linting and formatting JS/TS code.

For Swift code, we use [swift-format](https://github.com/swiftlang/swift-format) as a linter and formatter

For Objective-C, we use [clang-format](https://clang.llvm.org/docs/ClangFormat.html) as a linter and formatter

For Android, we use [Spotless](https://github.com/diffplug/spotless) and [ktfmt](https://facebook.github.io/ktfmt/) for linting and formatting

Our pre-commit hooks verify that the linter passes when committing.

### Publishing to npm

We use [changesets](https://github.com/changesets/changesets) to make it easier to publish new versions. It handles common tasks like bumping version based on semver, creating tags and releases etc.

### Scripts

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

- `yarn build:library`: compile the library code with babel.
- `yarn lint:js`: lint files with ESLint.
- `yarn typescript`: type-check files with TypeScript.
- `yarn lint:android`: lint Kotlin files.
- `yarn lint:objc`: lint Objective-C files.
- `yarn lint:swift`: lint Swift files.
- `yarn format:android`: format Kotlin files.
- `yarn format:objc`: format Objective-C files.
- `yarn format:swift`: format Swift files.

### 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](https://app.egghead.io/playlists/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.

## Code of Conduct

### Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

### Our Standards

Examples of behavior that contributes to a positive environment for our community include:

- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

- The use of sexualized language or imagery, and sexual attention or
  advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email
  address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a
  professional setting

### Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

### Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

### Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

### Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

#### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

#### 2. Warning

**Community Impact**: A violation through a single incident or series of actions.

**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

#### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

#### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the community.

### Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.