GroceryStore

Hybrid E-Commerce Application for managing the local Retailer Shop

Getting Started

Note: Make sure you have completed the React Native - Environment Setup instructions till "Creating a new application" step, before proceeding.

Step 1: Start the Metro Server

First, you will need to start Metro, the JavaScript bundler that ships with React Native.

To start Metro, run the following command from the root of your React Native project:

# using Yarn
yarn start

Step 2: Start your Application

Let Metro Bundler run in its own terminal. Open a new terminal from the root of your React Native project. Run the following command to start your Android or iOS app:

For Android

# Using Yarn
yarn android

For iOS

# Using Yarn
yarn ios

If everything is set up correctly, you should see your new app running in your Android Emulator or iOS Simulator shortly provided you have set up your emulator/simulator correctly.

This is one way to run your app — you can also run it directly from within Android Studio and Xcode respectively.

Step 3: Modifying your App

Now that you have successfully run the app, let's modify it.

1. Open App.tsx in your text editor of choice and edit some lines.

2. For Android: Press the R key twice or select "Reload" from the Developer Menu (Ctrl + M (on Window and Linux) or Cmd ⌘ + M (on macOS)) to see your changes!

   For iOS: Hit Cmd ⌘ + R in your iOS Simulator to reload the app and see your changes!

PR Flow will be as follows:

1. Create a new branch from develop branch.
2. When changes are done on your newly created branch then raise a PR to develop from your newly created branch.
3. Add a reviewer to the PR.
4. Attach the PR with the related issue
5. When review has approved then changes, then the PR will be merged to develop.

Note: Changes of develop branch will be merged to master by mentors

Steps to contribute:

• Clone the repository
• Production branch master
• Development branch develop
• Create new branch for each feature with type prefix ( Mind the casing ):
  • Types are as follows [ feature | hotfix | bugfix | release | docs ]
    • feature/user-authentication - For feature branch
    • hotfix/ticket-no-description - For any Hotfixes

Commit convention to follow:

• Specify the type of the commit as prefix and then write the commit message, examples as follows:
• Types are as follows: [ feat | docs | test | perf | chore | refactor | bugfix | hotfix | etc. ]
  • feat: "commit message"
  • bugfix: "commit message"
  • refactor: "commit message"
  • etc.

Happy Coding 😊