Sprint 4

.eslintrc.cjs

@@ -35,13 +35,14 @@ module.exports = {
     'react-hooks',
   ],
   rules: {
+    eqeqeq: 'error',
     '@typescript-eslint/no-floating-promises': [
       'error',
       {
         ignoreIIFE: true,
       },
     ],
-    eqeqeq: 'error',
+
     'operator-linebreak': ['error', 'after', { overrides: { '?': 'before', ':': 'before' } }],
     'no-console': 'warn',
     'no-undef': 'off',
@@ -92,6 +93,7 @@ module.exports = {
         allowConstantExport: true,
       },
     ],
+    'react/prop-types': 'off',
     'react-hooks/rules-of-hooks': 'error',
     'react-hooks/exhaustive-deps': 'warn',
     'jsx-a11y/label-has-associated-control': [

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.husky/pre-commit

@@ -1,3 +1,3 @@
-npm run format
-npm run ci:format
+npm run format --staged-files
+npm run ci:format --staged-files
 

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+Vadzim.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,49 @@
+**Welcome!**
+
+We're excited you're interested in contributing to our project! This guide outlines how you can get involved and make valuable contributions.
+
+**How to Contribute**
+
+- **Find an Issue:**
+  - Check our [Jira board ](https://megaandros.atlassian.net/jira/software/projects/DT/boards/2/backlog?epics=visible) for open issues.
+  - If you don't find a suitable issue, feel free to discuss new ideas by creating an issue in Jira.
+- **Claim the Issue (Optional):**
+  - Move issue to WIP status to let us know you're working on it. This helps avoid duplicate work.
+- **Work on the Issue:**
+  - Use the Confluence page linked in the issue for detailed specifications and discussions.
+  - Create branch. You can do it using link within Jira ticket.
+  - Feel free to ask questions in the comments section of the Jira issue or reach out to us directly.
+- **Create a Pull Request:**
+  - Once you've completed your work, create a pull request (PR) on GitHub. You can do it using link within the Jira ticket.
+  - Include a clear and concise description of your changes in the PR description. We have a template for PR.
+  - Reference the related Jira issue in your PR description for easy tracking. Just start all commits from Jira ticket number. Like `git commit -m "DT-100 Add new button"`
+- **Get Feedback and Iterate:**
+  - We will review your PR and provide feedback.
+  - Address any comments and iterate on your code as needed.
+
+**Pull Request (PR) Guidelines**
+
+- **Creation PR:**
+  - We use template for creation PR, just follow it
+  - Add screenshots for the smallest and biggest dimestions. See details in README.md
+- **Code Style:**
+  - Follow the existing code style and formatting conventions in the project.
+  - We used linter or code formatter like [ESLint](https://eslint.org/) and [Prettier](https://prettier.io/) to ensure consistency.
+- **Testing:**
+  - Write unit tests for your changes, if applicable.
+  - Existing tests should continue to pass after your modifications. We use Husky pre-push to run unit tests.
+- **Documentation:**
+  - Update any relevant documentation in Confluence if your changes affect functionality or usage.
+- **Clean Commits:**
+  - Use clear and concise commit messages that describe the changes you made or Comments in PR template.
+
+**Additional Considerations**
+
+- **Communication:**
+  - We value open communication. Feel free to ask questions, share ideas, and discuss challenges in the Jira issue comments or directly reach out to us. Use [discord](https://discord.com/channels/1233036099614543913/1233036100096884747) communication channel
+- **Attribution:**
+  - While we primarily use this project for learning, we appreciate proper attribution if you use or share any significant parts of our code.
+
+**Thank you for your contributions!**
+
+We appreciate your willingness to contribute to our project. By following these guidelines, you'll help us keep the project well-organized and maintain high-quality code.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Vadzim
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -13,33 +13,35 @@ It's a comprehensive online shopping portal that provides an interactive and sea
 1. Login and Registration pages 🖥️
 2. Main page 🏠
 3. Catalog Product page 📋
-4. Detailed Product page 🔎
+4. Product Detailed page (PDP) 🔎
 5. User Profile page 👤
 6. Basket page 🛒
 7. About Us page 🙋‍♂️🙋‍♀️
 
+## Layout
+
+We support layout from 380px till 1440px
+
 ## Technology Stack
 
-0. TypeScript
 1. React
 2. Vite
-3. Loadash
-4. AntDesign
+3. TypeScript
+4. Netlify
 5. SCSS
 6. HTML
 7. CSS
 8. CommerceTools - a leading provider of commerce solutions for B2C and B2B enterprises. CommerceTools offers a cloud-native, microservices-based commerce platform that enables brands to create unique and engaging digital commerce experiences.
 9. Linters: ESLint, Prettier, airbnb rules
 10. Husky
-11. git
-12. Jest
+11. Git/GitHub
 
 ## Organization
 
 0. Agile / Scrum
 1. Jira (Board, Dashboard, Releases, Sprint, Poker Planning, Automation)
 2. Confluence (Knowledge Base, MoMs, Agreements, Roles and Responsibilities etc..)
-3. GitHub (Pull Request, workflow, Review)
+3. GitHub (Pull Request, Workflow, Review)
 
 ## Design
 
@@ -141,7 +143,7 @@ npm run lint
 
 ### format
 
-start check of code quality with additional params. At the end you can find list of errors/warning in the terminal:
+to automatically format code using Prettier across all files in the src directory. This ensures consistent code style throughout the project.
 
 --cache - check only changed files
 
@@ -155,7 +157,7 @@ npm run format
 
 ### ci:format
 
-start check of code quality with additional params. At the end you can find list of errors/warning in the terminal:
+to check code formatting using Prettier across all files in the src directory. This helps identify formatting issues before committing changes.
 
 --cache - check only changed files
 
@@ -169,7 +171,7 @@ npm run ci:format
 
 ### test
 
-to run the test
+to run all tests
 
 Example:
 

SECURITY.md

@@ -0,0 +1,24 @@
+## SECURITY.md
+
+**Reporting Security Vulnerabilities**
+
+We take the security of our project seriously. If you discover a potential security vulnerability, please report it responsibly by following these guidelines:
+
+- **Do not disclose the vulnerability publicly.** Public disclosure could be exploited by attackers before a fix is available.
+- **Send an email to [rss.security.dreamteam@gmail.com]** with a detailed description of the vulnerability, including steps to reproduce it.
+- If possible, provide a proof-of-concept (POC) or exploit code (but do not include any attack scripts).
+- We will acknowledge your report within [acknowledgment timeframe, e.g., 48 hours] and work with you to understand the nature and severity of the vulnerability.
+
+**Supported Versions**
+
+We only consider security vulnerabilities affecting the following project versions:
+
+- [List supported versions, e.g., v1.x, v2.0]
+
+**Security Policy Updates**
+
+We will update this document as needed to reflect changes in our security practices or the project itself.
+
+**Disclaimer**
+
+This project is intended for educational purposes only. While we strive to maintain good security practices, we cannot guarantee the complete absence of vulnerabilities. We encourage you to use this project at your own risk.

package.json

@@ -12,7 +12,7 @@
   "main": "./src/main.tsx",
   "husky": {
     "hooks": {
-      "pre-commit": "lint-staged",
+      "pre-commit": "npm run format --staged-files",
       "pre-push": "npx validate-branch-name"
     }
   },