PAINTROID-490: Search bar on Landing Page

[chetanr25]

Ticket

JIRA Ticket - PAINTROID-490
Flutter: Search bar on Landing Page

This PR introduces a search functionality to the LandingPage that allows users to search for projects by name. The search feature includes a search toggle button and a search text field. When the search button is pressed, it hides the ProjectPreview and focuses on just the list of projects. The FloatingActionButton also hides as we go into search mode.

New Features and Enhancements

Added search bar functionality to search projects by name

Changes

1. Added SearchToggleButton Component:

   • Created a new SearchToggleButton component that toggles between a search icon and a close icon based on the search state.
   • The button triggers the start and end of the search functionality.

2. Added SearchTextField Component:

   • Created a new SearchTextField component that provides a text input field for users to enter their search queries.
   • The text field updates the search query state and filters the project list accordingly.

3. Updated LandingPage to Integrate Search Functionality:

   • Added search functionality in the LandingPage component.
   • Integrated the SearchToggleButton and SearchTextField components into the AppBar's title of the LandingPage.
   • Implemented logic to filter the project list based on the search query.
   • Modified the LandingPage to hide ProjectPreview and FloatingActionButton when in search mode.

Refactorings and Bug Fixes

• Fixed Bug with Project List Display:
  • Resolved an issue where only n-1 projects were displayed when n projects were saved.
    Removed unnecessary index != 0 condition to ensure all saved projects are visible.

catrobat.mov

Checklist

Your checklist for this pull request

Please review the contributing guidelines and wiki pages of this repository.

• Include the name of the Jira ticket in the PR’s title
• Add the link to the ticket in Jira in the description of the PR
• Include a summary of the changes plus the relevant context
• Choose the proper base branch (develop)
• Confirm that the changes follow the project’s coding guidelines (Wiki)
• Verify that the changes generate no compiler or linter warnings
• Perform a self-review of the changes
• Verify to commit no other files than the intentionally changed ones
• Include reasonable and readable tests verifying the added or changed behavior
• Confirm that new and existing tests pass locally
• Check that the commits’ message style matches the project’s guideline
• Verify that your changes do not have any conflicts with the base branch
• After the PR, verify that all CI checks have passed
• Add new information to the Wiki