Conversation
devleejb
approved these changes
Mar 2, 2024
devleejb
approved these changes
Mar 3, 2024
ykdy3951
deleted the
17-add-command-to-store-and-display-previous-search-history-in-database
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?:
enhancement
What this PR does / why we need it:
This PR implements a new command to allow users to store and display their previous search history in the database. This feature will provide users with the convenience of accessing their past searches easily and efficiently.
Which issue(s) this PR fixes:
Fixes #17
Special notes for your reviewer:
Users often find it helpful to refer back to their previous search queries for various reasons. By storing this information in the database, users can quickly retrieve and view their search history without the need to re-enter previous search terms repeatedly.
Does this PR introduce a user-facing change?
Additional documentation: