Sprint#1

[MakaevaElena]

Sprint 1: Repository Setup, Project Management, CommerceTools Integration, and Development Environment Configuration.

1. Task: https://github.com/rolling-scopes-school/tasks/blob/master/tasks/eCommerce-Application/Sprints/Sprint%231.md

2. Screenshot: -

3. Deploy: -

4. Done 05.08.2023 / Team deadline 05.08.2023 / Sprint deadline 07.08.2023

5. Score: 150 / 150

Mentor Evaluation Criteria (150 points - Total):

1. Repository Setup (29 points)

• (10 points) Create a GitHub repository for the project, complete with a README file, .gitignore, and necessary dependencies. RSS-ECOMM-1_01
• (10 points) Set up a clear and organized folder structure within the repository, ensuring a maintainable and scalable codebase. RSS-ECOMM-1_02
• (4 points) Invite all team members and the mentor as collaborators, ensuring everyone has access to contribute to the repository. RSS-ECOMM-1_03
• (5 points) Create a pull request template with a clear structure for describing proposed changes and the rationale behind them. RSS-ECOMM-1_21

2. Task Board Setup (Trello, Jira, etc.) (14 points)

• (6 points) Create a project task board using a project management tool (e.g., Trello or Jira), organizing tasks into lists or columns corresponding to their status (e.g., To Do, In Progress, Done). RSS-ECOMM-1_04
• (5 points) Break down project tasks into smaller, manageable subtasks and assign them to team members, ensuring a clear delegation of responsibilities. RSS-ECOMM-1_05
• (3 points) Share the task board with the team members and the mentor, ensuring everyone can track progress and update the status of their tasks. RSS-ECOMM-1_18

3. CommerceTools Project and API Client Setup (30 points) 💻

• (15 points) Create the project in CommerceTools, setting up the currencies, languages, and other configurations in the Merchant Center. RSS-ECOMM-1_06
• (15 points) Create the API client for CommerceTools, enabling access to the platform's APIs and managing permissions and scopes required for the project. RSS-ECOMM-1_07

4. Development Environment Configuration (43 points)

• (10 points) Set up and configure a bundler (e.g., Webpack, Vite, Parcel, or other) for the project, supporting both development and production build modes. RSS-ECOMM-1_08
• (5 points) Configure TypeScript to enforce strong typing and improve code quality throughout the project. RSS-ECOMM-1_09
• (5 points) Set up ESLint to enforce consistent coding styles and identify potential issues in the codebase. RSS-ECOMM-1_10
• (5 points) Configure Prettier to automatically format code, ensuring a consistent and readable code style. RSS-ECOMM-1_11
• (8 points) Initialize Husky to manage Git hooks, automating tasks such as code formatting and linting checks during the commit process. RSS-ECOMM-1_12
• (10 points) Install and configure Jest as the testing framework for the project, enabling comprehensive testing of code functionality. RSS-ECOMM-1_13

5. Development Scripts (15 points)

• (5 points) Create a script for running ESLint across the codebase, enabling quick and efficient identification of coding style issues and potential errors. RSS-ECOMM-1_14
• (5 points) Create a script for running Prettier across the codebase, simplifying code formatting and ensuring uniform code style. RSS-ECOMM-1_15
• (5 points) Create a script for running Jest tests, streamlining the process of executing tests and generating reports on test outcomes. RSS-ECOMM-1_16

6. Comprehensive README (19 points)

• (10 points) Add a thorough README file in the repository, describing the project, its purpose, and the technology stack used. RSS-ECOMM-1_17
• (5 points) Clearly document all available scripts (e.g., for running ESLint, Prettier, and Jest tests) and their usage in the README file. RSS-ECOMM-1_19
• (4 points) Provide detailed instructions for setting up and running the project locally, ensuring newcomers and contributors can quickly get started. RSS-ECOMM-1_20

[MikAleinik]

В данном ПР не организована структура каталогов проекта в соответствии с требованием RSS-ECOMM-1_02.
Необходимо до начала работы над вторым спринтом определить укрупненную структуру проекта. Пусть даже в дальнейшем вы будете вносить в нее корректировки, но на данном этапе каждый участник должен понимать где и какие файлы должны располагаться.