Updated logo and added multiple requests feature

[sudhz]

Added multiple requests feature

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

• [x] My code follows the code style of this project.
• [x] My change requires changes to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] All new and existing tests passed.
• [x] This PR does not contain plagiarized content.
• [x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

I'm still working on adding timestamp and url in each response.

[netlify[bot]]

✅ Deploy Preview for logiq ready!

Name	Link
🔨 Latest commit	b4656af8a2825af9836c47834546c3c5e6ff0e16
🔍 Latest deploy log	https://app.netlify.com/sites/logiq/deploys/652ee7deca0aaf0008c05e9a
😎 Deploy Preview	https://deploy-preview-40--logiq.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rufilboss]

How will the user input more than one URL?

[sudhz]

1. Enter one URL
2. Click on "Analyze"
3. The results are shown
4. Re-enter different URL
5. Click on "Analyze" again

After this, you'll see both the URL's results

[rufilboss]

Ohhh, awesome But can you also work on adding support to indicate the result of each request separately?

[rufilboss]

Addresses #40

[sudhz]

Do you mean to say that I should add the URL and timestamp in each response? Because the response is shown individually for each request.

[rufilboss]

Yeah, you get it

But I was thinking, adding the whole URL won't be that good as it might look nice, what do you think we can do?

[sudhz]

How about setting an ID for each request? Then displaying the ID?

[rufilboss]

Yeah

[sudhz]

Alright, I'll work on it

[sudhz]

Hi, instead of generating a unique ID for each request on the client side, wouldn't it be a better option to do it on the server side and send the response back with the ID? This is the response from the backend URL, which is https://logiqapi.onrender.com/api/analyze: As you can notice here, there is no ID property. Instead of setting a new unique ID on each request on the client side, wouldn't it be better if we handled it on the server side and sent a response like:

{
   "ID":"ccf7b488-9171-449f-aaca-5e36f94ef455",
   "URL":"https://google.com/",
   "isUp":true,
   "ipAddress":"142.251.33.78",
   "uptime":"99.00",
   "responseTime":"0.16"
}

Now, this would be for a successful response, when the URL is valid.

If the URL is invalid, your backend just sends the following response:

Instead of handling the invalid URL requests like this, you can send the response from the backend like:

{
   "ID":"ccf7b488-9171-449f-aaca-5e36f94ef455",
   "URL":"<the invalid url>",
   "isUp":false,
   "ipAddress":null,
   "uptime":null,
   "responseTime":null
}

What are your thoughts on this?

[rufilboss]

Yeah yeah, I want to said it ealier

[rufilboss]

Do you have time to work on it on the backend side?

[sudhz]

Yeah, sure, let me know the details