Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add local expo-cli for simulator.sh script #247

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Stukz
Copy link
Contributor

@Stukz Stukz commented Oct 4, 2023

Pull request type

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Description

New Expo CLI it's embedded in the Expo package, in order to use it we have to include it as devDep.

Updated simulator.sh script to support this


else
react-native run-ios --scheme $1 --configuration $2 ${@:3}
react-native run-ios --scheme $1 --mode $2 ${@:3}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this it's a new change introduced in react-native run command

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should also update this flag in all android:{env} scripts from package.json.

jpirazusta
jpirazusta previously approved these changes Oct 4, 2023
asdolo
asdolo previously approved these changes Oct 4, 2023
juanchoperezj
juanchoperezj previously approved these changes Oct 4, 2023
3. **Lint the app**: `yarn lint`
4. **Test the app**: `yarn test`

**Note: by default we use Expo CLI for iOS if you want to use react-native CLI you must append the following flag to the command:**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Note: by default we use Expo CLI for iOS if you want to use react-native CLI you must append the following flag to the command:**
**Note: by default we use Expo CLI for iOS. If you want to use react-native CLI you must append the following flag to the command:**


1. Rename your new project using `yarn rename` or `npm run rename`
2. Start on android or ios: `yarn android:{env}` or `yarn ios:{env}` (envs: `dev`,`qa`, `staging`, and `prod`)
2.1 You can also create `.env.prod`, `.env.staging`, and `.env.qa` to define environment variables for production and staging.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2.1 You can also create `.env.prod`, `.env.staging`, and `.env.qa` to define environment variables for production and staging.
2.1 You can also create `.env.prod`, `.env.staging`, and `.env.qa` to define environment variables for production, staging and QA.

npx pod-install
```

## Commands

1. **Start metro bundler**: `yarn start`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use an unordered list here?

Copy link
Contributor

@ramirogavagnin ramirogavagnin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:)

@@ -78,7 +79,8 @@ sonar-scanner \
-Dsonar.sources=. \
-Dsonar.projectBaseDir=. \
-Dsonar.javascript.lcov.reportPaths=coverage/lcov.info
-Dsonar.coverage.exclusions=**/spec.js,**/__mocks__/**,**/**.spec.js,**/**.config.js,**/rnbv.js,**/android/**,**/ios/**,**/**.styles.js,**/tests/**,**/__mocks__/**,**/httpClient/**,**/jest-setup.js,**/constants/**,**/assets/**,**/node_modules/**,**/coverage/**
-Dsonar.coverage.exclusions=**/spec.js,**/**mocks**/**,**/**.spec.js,**/**.config.js,**/rnbv.js,**/android/**,**/ios/**,**/**.styles.js,**/tests/**,**/**mocks**/**,**/httpClient/**,**/jest-setup.js,**/constants/**,**/assets/**,**/node_modules/**,**/coverage/**
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the change from __mocks__ to mocks might have been unintentional, because this project uses __mocks__ folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants