search

abhijeetnishal / URLShortener

URL Shortener Deployed Link 👇🏻
https://urlsrtner.vercel.app
MIT License
38 stars 62 forks source link

[feat] History of short URLs #197

Open SiddhiT28 opened 2 weeks ago

SiddhiT28 commented 2 weeks ago

Is your feature request related to a problem? Please describe. Shortened URLs are convenient, but tracking them can be challenging. A dedicated section to view all previously generated links would greatly enhance usability and help in maintaining a clear record of the shortened URLs.

Describe the solution you'd like A local storage variable can be implemented to maintain a record of the links from the previous four days. This tracking system would enable efficient retrieval and management of recently accessed URLs, ensuring quick access to historical data.

Describe alternatives you've considered We can have user management and track their URLs.

Additional context NA

github-actions[bot] commented 2 weeks ago

Congratulations, @SiddhiT28! 🎉 Thank you for creating your issue. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work!

We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines

SiddhiT28 commented 2 weeks ago

@abhijeetnishal can you please assign this issue to me under GSSOC 2024

abhijeetnishal commented 2 weeks ago

Hey @SiddhiT28, How do you planning to implement this feature?

SiddhiT28 commented 1 week ago

@abhijeetnishal My plan involves setting up a local storage system to maintain a log of the most recent 20 to 30 shortened URLs. This approach will ensure that the data remains within a manageable size. Subsequently, these URLs will be displayed below the input area for easy access and reference.

abhijeetnishal commented 1 week ago

Hey @SiddhiT28, Local storage is not a good approach for this, instead we will use persistence storage like database to store the urls for logged in users. If you want you can implement like this.

SiddhiT28 commented 1 week ago

Hey, @abhijeetnishal, I considered that option, but requiring users to log in might negatively impact the user experience. However, if you prefer, we can proceed with the database solution instead. Let me know your thoughts!

abhijeetnishal commented 1 week ago

Hey @SiddhiT28, but there are lot of other issues on storing in local storage, also db approach users can track all the past tracks.

How do you planning to implement have you seen the codebase, what all APIs are required, what UI needs to added?