Professional Documents
Culture Documents
VD Final Report Merged With PMMS
VD Final Report Merged With PMMS
VD Final Report Merged With PMMS
A PROJECT REPORT
Submitted by
VEDANT DARJI
190840131014
BACHELOR OF ENGINEERING
in
Computer Science and Engineering
R. N. G. Patel Institute of Technological, University
May, 2023
R. N. G. Patel Institute of Technology
Bardoli – Navsari Road, Isroli, Afwa, Bardoli, Gujarat 394620
CERTIFICATE
This is to certify that the project report submitted along with the project entitled
JavaScript Framework Training has been carried out by Vedant Darji under my
Disclaimer :
This is a computer generated copy and does not indicate that your data has been evaluated. This is the receipt that GTU
has received a copy of the data that you have uploaded and submitted as your project work.
*Guide has to sign the certificate, Only if all above activities has been Completed.
R. N. G. Patel Institute of Technology
Bardoli – Navsari Road, Isroli, Afwa, Bardoli, Gujarat 394620
DECLARATION
We hereby declare that the Internship report submitted along with the Internship
carried out by me at Narola Infotech Solutions LLP, Surat under the supervision of
Mr. Pratik Shah and that no part of this report has been directly copied from any
students’ reports or taken from any other source, without providing due reference.
1 Vedant Darji
ACKNOWLEDGEMENT
The satisfaction that accompanies the successful completion of this internship would be
incomplete without mentioning the people who made it possible, without whose constant
guidance and encouragement would have made efforts go in vain. I consider myself
privileged to express gratitude and respect toward all those who have guided me through
I convey thanks to my project guide Mr. Yash B. Naik, Computer Science & Engineering
support, and guidance which was of great help to complete this internship work
successfully.
I am grateful to my external guide Mr. Pratik Shah, Project Manager at Narola Infotech
Solutions LLP, Surat for giving me the support and encouragement that was necessary for
I am grateful to Dr. Madhavi Desai, Head of the Department, Computer Science &
Engineering Department, R.N.G.P.I.T for giving us the support and encouragement that
Patel Institute of Technology for providing us with a congenial environment to work in.
I would also like to thank the Placement Cell of the department for giving me an opportunity
to be a part of this internship. I extend my gratitude to all the faculty members for their
understanding and guidance that gave me the strength to work long hours for developing a
i
ABSTRACT
ii
List of Figures
Fig 1.1 Organisation Chart ............................................................................................ 2
Fig 2.1 Agile Methodology............................................................................................ 5
Fig. 3.1 Internship Timeline Chart .............................................................................. 11
Fig. 5.1 Use Case Diagram for the Google Keep Clone.............................................. 16
Fig. 5.2 User Data in JSON ......................................................................................... 17
Fig. 5.3 Note Data in JSON ......................................................................................... 17
Fig. 5.4 Flow Chart for Google Keep Clone ............................................................... 18
Fig. 6.1 Database Design for Fashion Point ................................................................ 20
Fig. 6.2 Database Mapping for Fashion Point ............................................................. 21
Fig. 6.3 Logic Flow for Rest Password ....................................................................... 21
Fig. 6.4 Query to Fetch Employee Records ................................................................. 22
Fig. 6.5 Stored Procedure Query ................................................................................. 23
Fig. 6.6 Stored Procedure Output ................................................................................ 23
Fig. 6.7 JS Task 1 Initial Rendering ............................................................................ 24
Fig. 6.8 JS Task 1 After Button Click ......................................................................... 24
Fig. 6.9 React Greeting Web Page .............................................................................. 25
Fig. 6.10 React Weather App ...................................................................................... 25
Fig. 6.11 React To-Do List Initial State ...................................................................... 26
Fig. 6.12 React To-Do List Adding Task .................................................................... 26
Fig. 6.13 React To-Do List Editing Task .................................................................... 26
Fig. 6.14 React To-Do List Deleting Task .................................................................. 27
Fig. 6.15 React To-Do List After Deletion .................................................................. 27
Fig. 6.16 Initial Student Registration Form ................................................................. 28
Fig. 6.17 Filled Student Registration Form ................................................................. 28
Fig. 6.18 Output of Student Registration Form ........................................................... 28
Fig. 6.19 User Registration Page ................................................................................. 29
Fig. 6.20 User Login Page ........................................................................................... 30
Fig. 6.21 Home Page ................................................................................................... 30
Fig. 6.22 Search Results .............................................................................................. 31
Fig. 6.23 Adding Note ................................................................................................. 31
Fig. 6.24 Note Section ................................................................................................. 32
Fig. 6.25 Before Edit Note........................................................................................... 32
iii
Fig. 6.26 Title Prompt.................................................................................................. 33
Fig. 6.27 Content Prompt ............................................................................................ 33
Fig. 6.28 Edited Note ................................................................................................... 33
Fig. 6.29 Before Delete Note ....................................................................................... 33
Fig. 6.30 Delete Confirmation ..................................................................................... 34
Fig. 6.31 After Delete Note ......................................................................................... 34
Fig. 6.32 Edit Profile Page........................................................................................... 34
Fig. 6.33 Edit Password Field ...................................................................................... 35
Fig. 6.34 Update Confirmation Alert........................................................................... 35
Fig. 6.35 Log-out Confirmation Alert ......................................................................... 35
iv
List of Tables
v
Abbreviations
vi
Table of Contents
Acknowledgment ............................................................................................................ i
Abstract .......................................................................................................................... ii
List of Figures ............................................................................................................... iii
List of Tables ................................................................................................................. v
List of Abbreviations .................................................................................................... vi
Table of Contents ......................................................................................................... vii
Chapter 1 Overview of the Company ........................................................................ 1
1.1 History.................................................................................................................. 1
1.2 Services Offered ................................................................................................... 2
1.3 Organisation Chart ............................................................................................... 2
1.4 Capacity of Organisation ..................................................................................... 2
Chapter 2 Overview of Different Departments of Organisation ............................. 3
2.1 Departments Overview ........................................................................................ 3
2.1.1 Technical Department ................................................................................... 3
2.1.2 Marketing Department .................................................................................. 3
2.1.3 HR Department ............................................................................................. 4
2.1.4 Management .................................................................................................. 4
2.2 Technical Specification of Systems Used ............................................................ 4
2.3 Development Process ........................................................................................... 4
2.4 Details about each stage of Development ............................................................ 5
Chapter 3 Introduction to Internship ........................................................................ 7
3.1 Internship Summary ............................................................................................. 7
3.2 Purpose ................................................................................................................. 7
3.3 Objective .............................................................................................................. 7
3.4 Scope .................................................................................................................... 8
3.5 Technology .......................................................................................................... 8
3.6 Internship Planning .............................................................................................. 9
3.6.1 Internship Approach.................................................................................... 9
3.6.2 Internship Effort and Time, Cost Estimation ............................................ 10
3.6.3 Roles and Responsibilities ........................................................................ 10
3.6.4 Group Dependencies ................................................................................. 11
3.7 Internship Scheduling ........................................................................................ 11
Chapter 4 System Analysis ............................................................................................ 12
vii
4.1 Study of Current System .................................................................................... 12
4.2 Problem and Weakness of the Current System .................................................. 12
4.3 Requirements of New System ............................................................................ 12
4.4 System Feasibility .............................................................................................. 12
4.5 Activities of New System .................................................................................. 12
4.6 Features of New System .................................................................................... 13
4.7 List of Reach Components ................................................................................. 13
4.8 Hardware and Software Requirements .............................................................. 14
Chapter 5 System Design .......................................................................................... 15
5.1 System Design and Methodology ...................................................................... 15
5.2 Database Design ................................................................................................. 16
5.2.1 User ........................................................................................................... 16
5.2.2 Notes ......................................................................................................... 17
5.3 System Flow Diagram ........................................................................................ 18
Chapter 6 Implementation ........................................................................................ 19
6.1 Implementation Platform ................................................................................... 19
6.1.1 React.......................................................................................................... 19
6.1.2 JSON Server .............................................................................................. 19
6.2 Process Specification ......................................................................................... 19
6.3 Result ................................................................................................................. 20
6.3.1 RDBMS Tasks .......................................................................................... 20
6.3.2 Core JavaScript Tasks ............................................................................... 24
6.3.3 React JS Tasks .......................................................................................... 25
6.3.4 Google Keep Clone Project....................................................................... 29
6.4 Result Analysis .................................................................................................. 35
Chapter 7 Testing ...................................................................................................... 36
7.1 Test Plan............................................................................................................. 36
7.2 Test Results and Analysis .................................................................................. 36
7.2.1 Test Case for Sign Up ............................................................................... 36
7.2.2 Test Case for Login ................................................................................... 36
7.2.3 Test Case for Note..................................................................................... 37
Chapter 8 Conclusion and Discussions .................................................................... 38
8.1 Overall Analysis of Internship ........................................................................... 38
8.2 Date of Surprise Visit by Institute Mentor ......................................................... 38
viii
8.3 Dates of Continuous Evaluation ........................................................................ 38
8.4 Problems Encountered and Possible Solutions .................................................. 38
8.4.1 Restrict the Access .................................................................................... 38
8.4.2 Reducing API Call and Handling Failures and Rendering ....................... 38
8.5 Summary of Internship....................................................................................... 39
8.6 Limitations and Future Enhancements ............................................................... 39
8.6.1 Limitations ................................................................................................ 39
8.6.2 Future Enhancements ................................................................................ 39
References ....................................................................................................................... 41
ix
287446 Overview of the Company
1.1 HISTORY
Narola Infotech Solutions LLP is a global IT solution provider company in India with
17+ years of competitive business experience in niche industries. It offers custom web
and mobile app design and development, backend development, enterprise services,
and CMS website development. Narola Infotech also has experienced professionals for
native iOS, and Android mobile applications & cross-platform technologies such as
Flutter and React Native. Narola Infotech Solutions LLP provides end-to-end support
for all our projects.
Vision
To empower our customers to achieve their goals by providing reliable and quality
solutions with technology and innovation.
Mission
To help entrepreneurs and creative thinkers convert their ideas into reality through the
power of emotional intelligence by providing world-class facilities to our team.
To deliver world-class products and services at competitive rates.
Narola Infotech Solutions LLP has a team of more than 350 talented IT Professionals.
OF THE ORGANIZATION
Narola Infotech is one of the leading outsourcing companies for web development. The
company helps potential clients to add significant value to their online presence. The
company plays a critical role in Promoting brand, business, and bottom-line expectations
from online assets.
The company serves these key market needs on Websites, E-commerce Stores, Web
Applications, and Mobile Applications.
• Technical Department
• Marketing Department
• HR Department
• Management
Each and every organization have a technical team that can design, develop,
and test a product. Technical Department also has a special team for support
which is responsible to solve technical problems in any organization.
o Product Design
o Website & App Development
o Maintenance and Testing of Product
o Technical Support
2.1.2 Marketing Department:
The marketing department is responsible for identifying, anticipating and
satisfying customer needs. The end goal is to make more profit. The marketing
the department is at the forefront as it interacts directly with the customers and
determines the success or failure of the company in generating revenue.
Narola Infotech has four departments under this section that are Business
Analyst, Digital Marketing, Direct Marketing & Sales Department.
2.1.3 HR Department:
An HR department is tasked with maximizing employee productivity and
protecting the company from any issues that may arise within the workforce. HR
responsibilities include compensation and benefits, recruitment, firing, and
keeping up to date with any laws that may affect the company and its employees.
2.1.4 Management:
This team is considered as apex team of the organization. The team consists of
all founders, co-founders, and CEO, CTO of the company. This team is
responsible for taking all the decisions regarding the company.
DEPARTMENT
Narola Infotech uses two Operating Systems that are Windows OS & Mac OS. Trainees
are allocated Mac OS.
The company’s methodology aims to deliver the right product, with incremental and
frequent delivery of small chunks of functionality, through small cross-functional self-
organizing teams, enabling frequent customer feedback and course correction as
needed. Requirements, plans, and results are evaluated continuously so our agile teams
have a natural mechanism for responding to change quickly.
• Brainstorm: During the brainstorming phase, the product owner determines the
scope of the project, prioritizes important projects if necessary, discusses key
requirements with the client, and prepares documentation outlining supported
features and proposed end results.
• Design: The design team puts their best effort into creating an impeccably designed
visual diaphragm for the software product based on client discussions and
expectations, as the visual appeal plays a major role in its success alongside
seamless functionalities.
• Development: During the development phase, the software solution/app idea is
executed by the developers who create a feature-rich product using their skills and
expertise, leveraging all necessary resources to ensure perfection, based on the
finalised design and agreed tech stack.
• Quality Assurance: Quality analyst team conducts both manual and automated
tests to ensure flawless software.
The internship program is designed to provide the students to engage in a field experience
with an opportunity to share their insights, explore the links between students' academic
preparation and their field work, and assist participants in developing and carrying out the
major research project which will serve to culminate their internship experience.
I joined Narola Infotech Solutions LLP on 01-02-2023. During the Internship, I was
able to explore various fields and aspects of web development, especially frontend
development. I got foundational training on RDBMS, where I got the opportunity to
learn database design for various systems, Queries, Join, and Stored Procedure. I got
to explore the JavaScript Core Concepts and the most popular library i.e., React JS. I
was also assigned tasks to create single-page applications like portfolio websites and
Google Keep Clone. I also got to explore various other libraries like material UI,
Bootstrap, AXIOS, SASS, Toastify, Formik, and Yup.
3.2 PURPOSE:
3.3 OBJECTIVE:
3.4 SCOPE:
3.5 TECHNOLOGY:
During the internship, I have learned all the following mentioned technologies. This
has been done in some or another way during the tasks assigned to me. To get familiar
with them, I have gone through various documentation and videos of the same and
implemented those.
Technologies:
➢ RBDMS: A relational database is a type of database that stores and provides access
to data points that are related to one another. Relational databases are based on the
relational model, an intuitive, straightforward way of representing data in tables. [1]
➢ XAMPP Server: It is an open-source package of web solutions that includes Apache
distribution for many servers and command-line executables along with modules such
as Apache server, MariaDB, PHP, and Perl. XAMPP helps a local host or server to test
its website and clients via computers and laptops before releasing it to the main server.
[2]
➢ HTML: HTML is the most basic building block of the Web. It defines the meaning
and structure of web content. Other technologies besides HTML are generally used to
describe a web page's appearance/presentation (CSS) or functionality/behavior
(JavaScript). [3]
➢ CSS: CSS is a stylesheet language used to describe the presentation of a document
written in HTML or XML. It describes how elements should be rendered on screen, on
paper, in speech, or on other media. [4]
➢ SASS: Sass is a stylesheet language that’s compiled into CSS. It allows you to use
variables, nested rules, mixins, functions, and more, all with a fully CSS-compatible
syntax. Sass helps keep large stylesheets well-organized and makes it easy to share
designs within and across projects. [5]
The entire internship was planned by the company. On the first day, they gave a basic
introduction to the company and guidelines about procedures followed in the company.
After that, we were allocated our desks. With each phase of training, they
communicated goals and learning objectives. An expert trainer was assigned in each
phase for our task review.
The entire internship carried out was a learning approach. It was divided into
three phases where phase 1 training was taken by the Director of Operations &
other phases of training were taken by Project Manager.
Internship Efforts:
Internship Time:
Cost Estimation:
Role Offered:
Responsibilities:
The entire internship tasks were assigned based on learning speed and tasks were
allocated by the trainer on an individual basis. Hence, there were no Group
dependencies and work was carried out by myself only.
Currently, Google Keep is available to only users having a Google account. To use this
service user either needs to create an account or needs to log in to use this service.
The new system is built for note taking which is similar to Google Keep. It allows only
logged-in users to create, read, update, delete, and search for a note. The main
requirement was to develop a user-friendly and responsive interface, also providing
security, authentication, profile management, note management, and search
functionality.
The new system provides users with the ability to manage their profiles which includes
registration, login, and editing their profiles. Users can also create, read, update, and
delete their notes within the note management system. Additionally, users can search
for notes using keywords from the header section, which includes matching titles or
content from their notes.
• In this system, there is a registration page, which has all fields required validation,
also it searches for email id in the database, if email exists then it will show error,
else user will be registered.
• The system allows to enter notes without content, the constraint in note is that title
can never be empty. If user doesn’t enter title, then title will be suggested as first
line of content.
• The system also restricts the homepage and other pages to logged in users, that is
system will be accessible only after successful log in.
Each task can be broken into smaller pieces or components. A Page can have many
Components. Following are a list of Components:
• Header: It displays the Header with Logo & Title. After Login, it includes a search
bar & user avatar also.
• Sign Up: It facilitates users to sign up for the system with basic details like name,
phone, email, and password.
• Login: It allows users to login into the system & perform CRUD Operations on
their Notes.
• HomePage: On this Page, all the notes of the user are shown, after login.
Note that HomePage & all functionalities are restricted to only logged-in users.
• New Note: It is used, to create a new note. A title is required while creating a new
note.
• Note: It is a component that contains the code to render a note. It is called repeatedly
to display all notes for the user.
• Search: Through this user can search for a note & perform various operations after
searching. Search is based on the title & the content in a note.
• Edit Profile: Users would be able to update their profile through this module.
• Hardware: The system is developed in company provided system i.e. in Mac OS.
• Software and Libraries Used:
Table 4.1 Software and Libraries Used
Name Used for
Visual Studio Code Development
JSON Server create a Fake RESTful API with a
JSON file to store data
npm JavaScript Package manager for
various dependencies
React Router Dom For Navigation between pages
Bootstrap and Material UI For attractive UI
• Before Login:
o User can register
o User can Login
• After Login:
o Header Section:
▪ Search for a note
▪ Update user profile
▪ Logout
o Main Note Section:
▪ Create a Note i.e., Add a Note
▪ View all Notes
▪ Edit a Note i.e., Update a Note
▪ Delete a Note
Fig. 5.1 Use Case Diagram for the Google Keep Clone
Since there is no database, the data is stored in JSON File called “NoteData.json”.
Through JSON Server fake Restful API Data is sent and receive in this File.
5.2.1 User:
Each object in this array of objects consists of 5 attributes that are as follows.
Table 5.1 User Data Format
Attribute Remarks
name Use to store user’s name
email Use to store user’s email
phone It stores user’s Phone Number
5.2.2 Notes:
Each element of notes consists of four attributes.
Table 5.2 Note Data Format
Attribute Remarks
u_id User Id of the User whose note it belongs to
id It is unique id for each note, with value of timestamp
converted to string.
title It stores title of that note.
Content It stores content of the note.
CHAPTER 6 IMPLEMENTATION
6.1.1 React:
React is a free and open-source front-end JavaScript library for building user
interfaces based on components. It is used to develop single-page, mobile, or
server-rendered applications with frameworks like Next.js. Because React is
only concerned with the user interface and rendering components to the DOM,
React applications often rely on libraries for routing and other client-side
functionality.
JSON Server is a lightweight server that allows you to quickly create a REST
API with JSON data. It can be useful for prototyping, testing, and mocking API
endpoints without having to set up a full backend server.
JSON Server is easy to use and requires minimal configuration. You simply
define your data as a JSON file, and JSON Server will create a fully functional
REST API based on that data. You can then use HTTP requests to interact with
the API and retrieve, create, update, and delete data. [15]
• User Initially Registers, in the system. If user email exists in database, it alerts Error
Message, else a unique id is generated and then this details are stored in database.
• After Registration, the user redirects to Login Page where the user logins with his
credentials. If the credentials are correct, a session storage is created with a user
name and user Id.
• If session storage exists, the user is allowed to access the home page.
• Through the Home Page, the user can search, read, create, edit, and delete a note.
User can also update their profile and can log out. During log-out, session storage
is cleared.
• Every operation is first performed on Client Side, its results are stored in local
storage and later API Call is made.
6.3 RESULT:
Task 1: To design a database for an application similar to Flipkart named “Fashion Point”
Output:
Task 2: To perform database mapping for an application similar to Flipkart named “Fashion
Point”
Output:
Task 3: To write flow and pseudo-code for a password reset for restaurant management
system.
Solution:
Task 4: Write a query to display the employees with their code, first name, last name and
hire date who hired either on seventh day of any month or seventh month in any year.
Query:
SELECT EMPLOYEE_ID,
FIRST_NAME,
LAST_NAME,
HIRE_DATE
FROM hrdemo.employees
WHERE MONTH(HIRE_DATE)=7 OR DAYOFMONTH(HIRE_DATE)=7
Output:
Task 5: For “myactivity” functionality we have “user_activity” table. In this table we have
records for different types of activities performed by the user. To maintain the activities in
this table, we have to call a stored procedure named as : “LOG_USER_ACTIVITY” from
all the places where activity should be logged.
Query:
Output:
JS Task 1: Change the HTML Button Style & Toggle its Style On Click Using JS
Output:
i) Before
Output:
Used Concepts: API, Input handling (use State and use Effect Hook)
Output:
Task 3: To Do List
Output:
Initial State:
i) Adding Task
After Deletion:
Concepts Used: Formik and Yup, useState and useEffect Hook, Routing Concepts
Functionalities: Seek the input of previous academic records for students i.e., take
standard, remarks, and percentage of classes less thanthe current standard.
Output:
Initial Render:
Suppose user selects current standard as 5th, then user will be asked to enter all academic
records till class 4th, after that only submit button will be enabled.
On Clicking Submit Button, user will be redirected to another page using routing concepts,
where entire details will be displayed.
➢ Registration:
➢ Login:
➢ Home Page:
• It is Page where all notes of the user are displayed & user can perform various
task like adding note, searching for note, deleting a note, editing a note from
this page.
➢ Search Bar:
➢ Add Note:
• User Will be able to add Note by entering title & Content in Note.
• To save Note user need to click on “+” Button.
• On Button Click, Note will be added in JSON File & Then the Note Section on
the Page Would be re rendered.
➢ Note Section:
• Note Section will be rendered for the number of objects / Notes present in Local
Storage.
• The Note Component is called using Map Function. So for every element (i.e.
Object) of Item in Local Storage, this Component will be called.
• So this Results in the Dynamically rendering of elements.
➢ Edit Note:
• With this Functionality, the User Can Edit a Note.
• On Clicking the Icon, two Prompts are displayed, One for Title & One for
Content.
• The value given in prompt is stored in new object. This Object is passed to API
Call using “PUT” Method.
• So this replaces existing object with New Object in JSON File for that id.
Before Edit:
• On Submitting, it the Data. The existing data in JSON File will be replaced with
New Data Object & again page will re -render.
• In image below, it can be seen that content & title is updated whose values were
given through Prompt.
➢ Delete Note:
• With this Functionality, User Can Delete a Note.
• On Clicking Delete Icon, Id of that Note is Passed & in JSON file with the help
of delete Method API Call, The Object in JSON File Gets Deleted.
• If user updates their password, they would be asked for confirm password for
the validation as seen in figure below.
The project can provide an easy and convenient way for users to manage their notes
and tasks, which can help increase their productivity. Additionally, the ability to
customize user profiles as and when they want can help users feel more invested in
the application and create a sense of ownership. The security features implemented
in the project can ensure that user data is protected, and restricted to the user itself
which in turn creates a safe and trustworthy environment for users. Overall, the
Google Keep clone project can result in improved user experience, increased
productivity, and a sense of security and ownership for users. While there is scope of
improvement by implementing concepts of encrypting data in every phase, but the
application at its current version provides a strong foundational base for future
development and enhancements.
CHAPTER 7 TESTING
As a Developer, it is very crucial to check the system from the end user’s point of view
and validate inputs. Through this activity, we can generate a set of test data to test the
new system before accepting it. During this test generation phase, all parts and end
cases are considered to ensure the system does not produce any errors. If there are
errors, we remove them and then test them again until a bug-free system is found.
Various parts of the system are tested which are as mentioned below.
Here various scenarios for login page are considered and tested.
In this various test have been performed on note operations based on User’s
Perspective.
Visit 1: 27-03-2023
Visit 2: 05-05-2023
Since, the data stored in the Notes can be precious, So It was important to Restrict
the access to HomePage and user should be displayed only their Notes. This
problem was solved by using local & Session Storage. User will be able to visit
homepage only when the user is logged in.
8.4.2 Reducing API Call and Handling Transmission Failure & Rendering:
The main goal was to reduce the load on server and re render components when
there was any change. So This was solved by First updating local & Session
Storage then send the updated object through API. So in case of failure again we
can retry by retransmitting data through API. Also, Validations are performed on
the Client End so Server won’t have enough Load for Validation. Its role would
be To perform CRUD Operations.
During the 12 Weeks Internship, I got to learn many libraries used in frontend web
Development. I also got a chance to brush up my foundational Concepts on RDBMS. I
got to learn about Core JavaScript Concepts and focus on Few mostly used methods
of it which are useful in Frontend JS. I got to know about React Library and understand
each concept by performing a few learning tasks.
After learning all these concepts, I got a chance to implement this concept of JS &
React to create a Web Application like Google Keep Clone. In this Project, I divided
each functionality into components and learned about passing data from one
component to another. I have used Fake API (i.e., JSON Server) to send/Receive data
into a JSON file. In this File, I am storing data of User and Notes. The Project, allows
user to Perform CRUD Operation of any Note.
During the training, I also Learnt about various libraries like material UI, Bootstrap,
Axios, SASS, Toastify, Formik and Yup.
8.6.1 Limitations:
o The Data sent via API are not encrypted i.e. No Encryption or Decryption
Algorithms are used for transmitting data. So, This can cause Issues in Privacy.
o There is no Facility to Pin a Note.
the file as JSON, then I will be using MongoDB Cloud which stores data in JSON
Format.
o In the Future, the Format of Notes can be changed to Add image/ List view which
is not currently developed.
o Sharing of Notes to other users also.
REFERENCES
[15] “typicode/json-server: Get a full fake REST API with zero coding in less than 30
seconds (seriously).” https://github.com/typicode/json-server (accessed May 09,
2023).