react-native-ultimate-config

_Config that works_


_Project generated with https://github.com/brodybits/create-react-native-module_

Suport of gradle

| react-native-ultimate-config | gradle |
| ---------------------------- | ------ |
| ^3 | <=6 |
| >4 | 7 |

TL;DR usage

1. install
|npm | yarn |
|-|-|
|npm install react-native-ultimate-config | yarn add react-native-ultimate-config|
2. one-off setup for native projects
3. initialize env
|npm | yarn |
|-|-|
|npm run rnuc |yarn rnuc |
4. build! react-native run-{ios,android}

☝❗Approach to versioning and breaking changes

This library is using semver and heavily relying on codegeneration. Many new features and/or bugfixes will require these files to be regenerated. Changes to codegenerated files will not be considered breaking
unless they affect behavior of API or CLI.

Therefore every time this library is updated all files MUST be regenerated using rnuc command.

Table of contents

1. Features 🎆
1. Mission 🥾
1. Quickstart Guide 🏃
1. API 🧰
1. Changelog 📓
1. Cookbook 🥦
1. Troubleshooting 🎱
1. Contributor notes
1. Alternatives

Features

1. Simple one-off setup for native projects
1. No need to mess with xcode schemes or android flavors
1. Access from javascript
1. Access from native code: java and objective-c
1. Access in build tools: xcode, gradle and AndroidManifest.xml
1. Web support (works with React Native for Web)
1. Hooks
1. Monorepo support (yarn workspaces or lerna)
1. Unit tested with jest
1. E2E tested with detox
1. Provides typescript typings
1. Supports dotenv and yaml
1. Fully typed values available when using yaml config
1. Configure values per platform in one file

Mission

React-Native brings together 3 platforms: ios, android, javascript each of
which have different conventions and approaches how to manage environment
settings.

A typical app is usually operating in some environment defined by server urls
various api keys or feature flags. When dealing with react-native such things
often need to exist in 3 places: ios, android and js code. Even managing things
as simple as application name or bundle id needs to be done in 2 places:
Info.plist and AndroidManifest.xml

react-native-ultimate-config tries to reduce friction in managing these things
by abstracting away from nuances of native projects.

With react-native-ultimate-config it is possible to consume variables in
every place of a typical react-native app:

- javascript
- native code
- java
- objective-c
- native build configuration
- ios
- build settings
- infoplist
- android
- build config
- string resources
- project.ext

``
|-------------------------------------------------------|
| |
| javascript |
| |
|-------------------------------------------------------|
| | |
| objective-c | java |
| | |
|-------------------------------------------------------|
| | |
| build settings | AndroidManifest.xml |
| infoplist | build.gradle |
| | |
|-------------------------------------------------------|
``