Frontend Part using ReactJS for Nectus 🚀

[yezz123]

Setup The FrontEnd Part

#change Directory to Frontend
$ cd Frontend

# Prepare the environment by Installing all the Packages
$ npm install package.json

• If all the Packages are installed and you see node_modules Folder Start :
• if you feel there is no error in the settings of .env.
• make sure the API url is correct.
• If you feel that everything can be run, then run Frontend Part.

# Build the Project
$ npm run build

# Start The Project
$ npm run start

• default port http://localhost:5000/

REACT_APP_URL_API = http://localhost:5000

[pull-request-quantifier-deprecated[bot]]

This PR has 1383 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Large
Size       : +1362 -21
Percentile : 100%

Total files changed: 27

Change summary by file extension:
.json : +422 -1
.dockerignore : +22 -0
.gitignore : +18 -0
.html : +39 -0
.txt : +3 -0
.css : +46 -0
.js : +95 -0
.jsx : +642 -0
.svg : +8 -0
.md : +56 -20
Frontend/Dockerfile : +11 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[yezz123]

I will try to improve the style and The .css file for the Project to Create a good Design for the Frontend Part for the Project :rocket: