history of all requests

[spnaik66]

feature like Request Logging, Response Logging,Timestamps,Clear History

[Ivan2001otp]

I would like to fix this issue. Please assign this issue to me. @ashitaprasad

[ashitaprasad]

@Ivan2001otp, We do not assign issues. You are free to work on it and send across a PR.

[nikkivirtuoso]

in this issue do we have to maintain the whole history or simply maintain the history upto that session ? Just asking as, if we want to maintain the whole history we will use the list and that will make the working slow as it has to track all the history and then display it, if we want to maintain history for particular session this will not affect the speed

[animator]

@nikkivirtuoso Usually history maintains the entire history (upto certain number of days like 1 week, 1 month, etc. that can be set by the user) & not just the session history.

[nikkivirtuoso]

so we can do something like this:

[nikkivirtuoso]

moreover, we can show whether the request was successful in getting the POST method or not but first we have to implement this in our application for that we can make a seperate window for the history like making a icon just below the requuests icon in the vertical appBar( left side of the application) and when user click on it (if he/she wants to check the history) then we can display the history like this
Please have look on this 😊

[nikkivirtuoso]

Screen.Recording.2024-02-26.at.1.41.10.PM.mov

here is the video, all the parameters i Have created is to look cool ( no other reason) we can have something like this,

[animator]

@nikkivirtuoso think of the UI design in respect to API Dash, integrate your solution in it and send across a PR for feedback.

[dhruvpatidar359]

Hi Maintainers , i was thinking for UI something like this .

[ashitaprasad]

@dhruvpatidar359 , looks good 👍

[dhruvpatidar359]

ok , so i will be needing help in writing the test cases for this . Will be opening a PR soon.

[dhruvpatidar359]

I have implemented some sort of functionality in this . I need the UI part of the collections , so that it will be consistent . Right now the UI part is not available where i can find it by the way.

This part i am looking for .

[animator]

@dhruvpatidar359 Kindly rethink the UI design of this section as this is neither user friendly nor shows the true purpose of the section.

• What are the most important things for the user which will make him/her visit this section?
• Why is the request pane same as the requests section? How is it helping the user?
• Do I want to see failed requests? Do I want to see successful requests? How can I see it at a single glance.
• Do I allow sending requests from this section?
• What is the purpose of arranging it like a collection. Is it serving any purpose. Can't it just be an expansion list which will be more effective or do I need today, yesterday grouping at all?
  These are just some of the question you might be asking and need to think more on this feature.

[dhruvpatidar359]

Ok,
1 ) For your first question : I think , if user want to see the response of his multiple queries and want to some comparisons kind of operations then he/she may need it .
2 ) For the second one : We may just keep the response and provide a button to take this particular request into the Requests panel for re-running the query
3 ) For your third question , we can provide a kind of functionality where the person can sort on the basis of fail | success or any other kind of parameter.
4 ) If we want the person to send the request from this section , then i think we should remove this particular section and provide a top bar where the person can see the currently issued requests and the history is just located on the side bar .

5 ) We should have today , yesterday ... sort of grouping as it make the navigation faster for the person , otherwise it will become mess.

[animator]

@salahu01 comment on this issue in #384

Currently, Api Dash requires users to manually save each API request. This can be cumbersome, especially when working with multiple requests or iterating through different configurations. Postman, a popular API testing tool, offers automatic request history with the ability to name and organize requests for easier access and reference.

Implementing automatic request history and management in Api Dash would significantly improve its usability. This feature could include:

• Automatically saving past API requests with timestamps.
• Allowing users to name and organize saved requests for better management.
• The ability to filter and search through saved requests.

This functionality would make Api Dash a more efficient and user-friendly tool for developers and testers working with multiple APIs.