Skip to content

Latest commit

 

History

History
56 lines (36 loc) · 2.29 KB

README.md

File metadata and controls

56 lines (36 loc) · 2.29 KB

MoToDo

js-standard-style

  • ToDo list React Native App Utilizing Ignite
  • Android version only

⬆️ How to Setup

Step 1: git clone this repo:

Step 2: cd to the cloned repo:

Step 3: Install the Application with npm install

Step 4: Go to node_modules/babel-preset-react-native/configs/main.js and remove line 41: require('../transforms/transform-symbol-member'),. This is the conflict of current versions of rxjs 5.rc4 and babel (25/11/2016).

Step 5: add:

compile 'com.google.firebase:firebase-core:+'
compile 'com.google.firebase:firebase-messaging:+'

into "node_modules/react-native-system-notification/android/build.gradle"

Step 6: you also might need to give 777 access rights to the file \node_modules\react-native\android\com\facebook\react\react-native\0.38.0\react-native-0.38.0.aar

▶️ How to Run App

  1. cd to the repo
  2. Run Build for either OS
  • for iOS
    • run react-native run-ios
  • for Android
    • Run Genymotion
    • run react-native run-android

🚫 Standard Compliant

js-standard-style This project adheres to Standard. Our CI enforces this, so we suggest you enable linting to keep your project compliant during development.

To Lint on Commit

  1. Install git-hooks => On a Mac brew install git-hooks - Other
  2. Setup on Repo => git hooks --install

Bypass Lint

If you have to bypass lint for a special commit that you will come back and clean (pushing something to a branch etc.) then you can bypass git hooks with adding --no-verify to your commit command.

Understanding Linting Errors

The linting rules are from JS Standard and React-Standard. Regular JS errors can be found with descriptions here, while React errors and descriptions can be found here.

📂 Related Articles

Ignite Documentation - Ignite Wiki https://github.com/infinitered/ignite/wiki