/DevShop

E-Commerce: Uma versão mobile do aplicativo web, que permite ao usuario visualizar e adicionarem produtoss ao carinho e fazerem compras

Primary LanguageTypeScript

E-commerce Mobile Store

Capa (4)

Fetures

  • The user will be able to add product to cart
  • The user will be able to checkout
  • The user will be able to search products
  • The user will be able to search products by category

Technologies

To build this project we are using the following technologies:

Getting Started

Make sure you have the Ecommerce Admin setup first!

Prerequisites

To get started you must have the following softwares installed:

Instalation

Open a terminal follow the steps bellow

  1. Clone the repository:
 $ git clone https://github.com/room-organization/DevShop.git
  • Got to the project directory
2. cd DevShop
  1. Install depedencies
npm install
  1. Install expo cli
npm install -g expo-cli
  1. Setup .env file
# You will find this on Ecommerce-Admin
NEXT_PUBLIC_API_URL=
  1. Start the app
expo start

# Or

npx expo start

Note:aMake sure you run the Ecommerce Admin first!

Contributing

Follow these steps to make your contribution.

Create a new branch

  1. Create a new branch for your changes. The branch name should start with one of the following prefixes, depending on the type of changes you are making:
    • feat/ for new features
    • fix/ for bug fixes
    • docs/ for documentation changes
    • style/ for changes that do not affect the meaning of the code (e.g. formatting)
    • refactor/ for code changes that neither fix a bug nor add a feature
  2. Make your changes and commit them using Conventional Commits.
  3. Push your changes to your feature branch.
  4. Create a pull request and use the dev brach as a base branch.

Convetional commits

We use Conventional Commits to standardize our commit messages. Please follow the guidelines below when making your commits:

  1. Use the following format for your commit messages: <type>(<scope>): <subject>.
  2. The must be one of the following:
    • feat: a new feature
    • fix: a bug fix
    • docs: documentation changes
    • style: changes that do not affect the meaning of the code (e.g. formatting)
    • refactor: code changes that neither fix a bug nor add a feature
    • perf: code changes that improve performance
    • test: adding missing tests or correcting existing tests
  3. The <scope> is optional and should be used to specify which part of the project your commit affects.
  4. The <subject> should be a short description of the change.

Your contributions are valuable to us and we appreciate your efforts to make this project better.

Happy contributing ;)