-
-
Notifications
You must be signed in to change notification settings - Fork 54
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix #83
- Loading branch information
Showing
13 changed files
with
124 additions
and
88 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,36 +1,21 @@ | ||
# <%= props.name %> | ||
[![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg?style=flat)](http://standardjs.com/) | ||
|
||
* Standard compliant React Native App Utilizing [Ignite](https://github.com/infinitered/ignite) and [Ignite Jhipster](https://github.com/ruddell/ignite-jhipster) | ||
* React Native app generated with [Ignite Jhipster](https://github.com/ruddell/ignite-jhipster). See the Ignite JHipster docs for more details regarding this boilerplate. | ||
|
||
## :arrow_up: 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 3:** Install the Application with `<%= useNpm ? 'npm' : 'yarn' > install` | ||
|
||
|
||
## :arrow_forward: How to Run App | ||
|
||
1. cd to the repo | ||
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` | ||
|
||
## :no_entry_sign: Standard Compliant | ||
|
||
[![js-standard-style](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard) | ||
This project adheres to Standard. Our CI enforces this, so we suggest you enable linting to keep your project compliant during development. | ||
|
||
**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](http://eslint.org/docs/rules/), while [React errors and descriptions can be found here](https://github.com/yannickcr/eslint-plugin-react). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
## Detox | ||
- Currently, Detox only supports iOS/macOS and does not support tests requiring authentication for OAuth2 apps. | ||
|
||
If enabled during generation, [Detox](https://github.com/wix/Detox) is configured for the project. Sample tests are available for the account screens, and are generated for entity screens when you add an entity. For example: | ||
|
||
- [`e2e/settings-screen.spec.js`](https://github.com/ruddell/ignite-jhipster/blob/53d1d3e9cd5bd4fbba5ca8b20d7334a9b7ad24f4/boilerplate/e2e/settings-screen.spec.js) | ||
- [`e2e/login-screen.spec.js`](https://github.com/ruddell/ignite-jhipster/blob/master/boilerplate/e2e/login-screen.spec.js) | ||
|
||
To run the tests, you need to build the app for debug or release: | ||
```bash | ||
detox build --configuration ios.sim.debug | ||
detox build --configuration ios.sim.release | ||
``` | ||
Then run the tests using the same configuration from above: | ||
```bash | ||
detox test --configuration ios.sim.debug --reuse | ||
detox test --configuration ios.sim.release --reuse | ||
``` | ||
|
||
For more information on configuration and writing tests for Detox, check the [official Detox documentation](https://github.com/wix/Detox/blob/master/docs/README.md). | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
## Fastlane | ||
- Currently, fastlane is officially supported to run on macOS. | ||
|
||
[Fastlane](https://github.com/fastlane/fastlane) automates building and releasing your mobile apps. It can handle all tedious tasks, like generating screenshots, dealing with code signing, and releasing your application. | ||
|
||
The Fastlane files are generated under the `fastlane` folder at the root of the project. When running Fastlane, the outcome depends on the platform: | ||
- For iOS, provisioning profiles are checked/updated, the app is built, signed with release keys, uploaded to Testflight, and released to beta testers. | ||
- For Android, the app is built, signed with release keys, uploaded to Google Play, and released to a beta track. | ||
|
||
### Fastlane Config | ||
#### Appfile | ||
Contains information identifying your app. | ||
|
||
#### Fastfile | ||
Fastlane uses a "lane" concept, which is basically a function. A lane contains logic for building and uploading your app to the app stores. The generated Fastfile contains two lanes, one for each platform (iOS and Android). | ||
|
||
#### Matchfile | ||
Used for [Fastlane Match](https://docs.fastlane.tools/actions/match/), which shares one code signing identity across your development team to simplify your codesigning setup and prevent code signing issues. | ||
|
||
|
||
### Running Fastlane | ||
To run the iOS lane: | ||
```bash | ||
fastlane ios build | ||
``` | ||
To run the Android lane: | ||
```bash | ||
fastlane android build | ||
``` | ||
- **Note**: You must upload the first AAB/APK file to Google Play manually before using Fastlane. | ||
|
||
For more information on configuration for Fastlane, check the [official Fastlane documentation](https://docs.fastlane.tools/). |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
### Generators | ||
|
||
#### Entity | ||
|
||
`ignite generate entity <name>` | ||
- Prompts for the path to the entity's config (`.jhipster` folder in your app) | ||
- Generates all files needed for fetching and displaying the entity | ||
- Includes the API endpoints, redux/saga config, and the user interface | ||
|
||
#### Import JDL | ||
`ignite generate import-jdl <jdl-filename>` | ||
- Import several entities at once using JDL | ||
- Runs the entity generator for each entity present in the JDL | ||
|
||
#### Upgrade | ||
`ignite generate upgrade` | ||
- Upgrades your generated app to the latest template code. Make sure to upgrade `ignite-jhipster` in your `package.json` first. | ||
- It's recommended to use `git` and branches to merge changes into your code. | ||
- The command below will keep all of your changes while merging any updates. If there are conflicts, you will need to manually merge the changes. | ||
- `git merge -s recursive -Xours <branch name>` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
## Storybook | ||
Storybook for React Native is configured out-of-the-box in DEV builds only (local device or simulator). You can access it in the Side Menu by clicking on "Storybook". | ||
|
||
### Stories | ||
Sample "stories" are available for the generated components. They allow you to preview the components in various states, dependant on the props passed to them. | ||
|
||
- [`search-bar.story.js`](https://github.com/ruddell/ignite-jhipster/blob/53d1d3e9cd5bd4fbba5ca8b20d7334a9b7ad24f4/boilerplate/app/shared/components/search-bar/search-bar.story.js) | ||
- [`alert-message.story.js`](https://github.com/ruddell/ignite-jhipster/blob/master/boilerplate/app/shared/components/alert-message/alert-message.story.js) | ||
|
||
Use fixtures (JSON files containing sample data) to write stories for your own components. | ||
|
||
For more information on configuration and writing stories for Storybook, check the [official Storybook documentation](https://storybook.js.org/docs/guides/guide-react-native/). | ||
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters