GSoC'23 Journey

shubhangi013 — Mon, 19 Jun 2023 13:02:11 +0000

May 28, 2023 - Jun 3, 2023

After getting added to all the resources, updated my monday with further broken down tasks and weekly sprints
This week was dedicated to knowing about the platform, the needs of the users and brainstorming about the problems in the current UI. The following were the results of it-

Give a visual overview of the profile
Make the sidebar better by giving more apparent names
Dns_Resolution is not showing up in the table
Tags are pretty broken in general
Hotkeys should be enabled to navigate
Add columns for hostname on the timeline
Resize the columns and optimize the space

I started with prioritizing what should be done first and researched about online frameworks and libraries available to achieve them and decided on keeping bootstrap as the primary one.
I added debug mode in the web interface for the future developers
I started with a Figma mockup

Jun 4, 2023 - Jun 11, 2023

I was sick for most part of the week but when I got back not only did I catch up, but also went ahead to implement a design for the navbar I’ve been working on.
I embedded the documentation and have opened a pull request for the same.
Next on I plan on working on fixing the bugs and

Jun 12, 2023 - Jun 19, 2023

I designed the 2nd navbar on Figma and side by side implemented it on code. I didn't install any other library and used the pre-installed bootstrap. I've now been working on making the sidebar more responsive. I've figured out the way I can achieve this and now I'm implementing it and plan on opening a PR for the same. I tried to solve the bugs i was assigned, but couldn't replicate the errors.
I'll focus on creating further tasks revolving around the general profile/ the sidebar and solving bugs side by side. The overall design is focussed on extracting colors from the stratosphere logo and using them.

Jun 20,23 - Jun 26,2023

I've designed the IP overview and have made significant progress in profile overview and general overview.
I need some more information and will be good do go with complete design.

Jun 26,23 - Jul 3,2023

With the help from my GSoC mentors, I have finally designed all the 3 screens and will implement them now. Figma has proven to be an excellent tool with its community feature and ability to collaborate easily.
I created a spreadsheet to ease the process of grouping certain components together.

APIs 101 with Postman

shubhangi013 — Tue, 28 Sep 2021 11:50:33 +0000

Image source:here

‘Application Programming Interface’: The name sure is intimidating!
As someone who is fascinated by constant tech developments, how everything is becoming more sophisticated yet simplified, I find APIs very captivating. I was looking forward to learning more about them and the platform I use the most while working with them: Postman. With the
‘APIs 101 with Postman’ organized by The Club of Programmers, IIT (BHU) and hosted by @king11 , we all got an opportunity to hone our existing knowledge and learn new ones.

INTRODUCTION

The session kicked off with Lakshay Bhaiya taking up our branch names as the ‘ice-breaker’ XD.
He asked us to put up our branch name on the chat. AND…
Drum Rolls
The PPT rolled off with a comparison between a restaurant and how the ‘client-server’ system works. The server was compared to the Chef and the client was the person who ordered the food.
The example compared the APIs with a waiter. Hence, an API bridges the gap and enables communication between the client and the server.

Next, from the ‘not-so tech example', we moved on to the technical definition of an API.

Application Programming Interfaces (APIs) allow services to communicate with each other.

This put into perspective what exactly is the role of an API and how easy Postman makes it for us to work with them. One can use their terminal to work with an API but for a better experience and efficient workflow, Postman has proven to be a useful platform.

The session continued with an analysis of how requests are made and responses are received.
I’ve worked with APIs and Postman multiple times before but this session gave me a clearer idea of what I do while sending or retrieving data via APIs. The whole understructure of every application we use rely on the APIs, this itself speaks volumes about why one must invest time in learning about them.

HANDS-ON EXPERIENCE

After a PPT-oriented introduction and constant quizzing by bhaiya on simple concepts (which made the session fun!), we moved on to a hands-on experience of working with a simple API.
Here is the link to the whole set-up.

Using the endpoint URL,we chose to work with the path ‘/joke’ (because why not!?): a random joke would come up with GET requests to the API. Needless to say, we crashed the server XD, a probable reason: too many requests being sent at once to it.
A major takeaway from this section was how the major methods: GET, PUT, PATCH and POST work.

HTTP VERBS :

GET : This method requests the resource
POST : This method is used to 'submit' or 'create' a resource
PUT : This method is used to 'replace' an existing resource or 'create' one if not found
PATCH : This method is used to 'modify' an existing resource and is required to contain only the changes to the resource
DELETE : As evident by it's name, this method is used to delete the specified resource

DIFFERENCE BETWEEN `PUT` AND `PATCH` METHODS :

Although both these methods are used to update the existing data, they are different in terms of the extent to which they modify the data. PUT method updates the entire resource or creates a new one if it already doesn't exist, whereas PATCH method updates partial-data as sent by the client or throws exception when the resource is not found.
As an example, consider the following code snippet :

     axios({
         headers: {
             Authorization: "Token " + localStorage.getItem("token")
         },
         url: API_BASE_URL + "todo/" + id + "/",
         method: "patch",
         data: { title: taskEntry }
     })

It's a snippet from a function that updates task in a To-Do web-app. I've used the PATCH method here because I wanted the function to update just the task the user wanted to update.
You can find the entire function and the rest of the methods I've used here.

To learn more about these methods, I would recommend you to visit this link

The session also gave clarity regarding the Params, Body, Header, and everything one can spot or could have a query for while working with an API in Postman.

After an amazing experience, the session came to an end :(
Postman is really a great platform to work with APIs.

Build them, test them and have FUN while doing it!

DEV Community: shubhangi013