CineSearcher Phase 1

You need to track your commits and changes in your GitHub repository. To get started with setting up your repository, first create a new repository in your GitHub account and name it CineSearcher. Once that's done, you'll need to set up your local repository. To do this, open your terminal and run git init in your project directory to initialize the local repository. This step helps track all the changes you make in your code.

Before you begin coding, take some time to thoroughly review the project requirements and create GitHub issues for each task you plan to work on. Each task should have its own GitHub issue, and these issues should be written in the future tense. For example, if you're working on a feature to add a search bar, then raise a GitHub issue titled Add search bar. This helps you stay organized and track what needs to be done.

Next, when you're ready to start working on a task, you'll need to create a branch. Branches are used to separate your work from the main codebase, making it easier to manage different features. Branch names should be written in the future tense and follow a simple format, like this: <issue_number>-add-search-bar. This way, you can easily link each branch to the relevant GitHub issue.

To create a new branch, run the command git checkout -b <issue_number>-add-search-bar. This creates and switches you to a new branch.

When you're making changes, it's important to commit them regularly. A good rule of thumb is to make small, logical commits. Instead of committing all your changes for a task in a single commit, break your work into smaller parts and commit after completing each part. This helps make your progress easier to follow. Always use meaningful commit messages, such as Added CSS styling for the search bar or Fixed search bar flicker issue. Use past tense and avoid vague messages like Completed first part.

Once you've made your changes and committed them to the branch, you'll need to create a Pull Request (PR). A PR is a request to merge your changes into the main branch. To create the PR, first push your branch to GitHub by running the command git push origin <issue_number>-add-search-bar.

After pushing the branch, go to your GitHub repository, where you should see a prompt to create a Pull Request for the branch you've just pushed. Click the Compare & Pull Request button, add a title and description for the PR. When you write PR titles, use the past tense. For example, Added movie card or Fixed re-rendering issue of the view history component. In the PR description, add Fixes #<issue_number> to automatically close the issue when the PR is merged.

Finally, when you're working with branches, it's best to always create a new branch from the main branch for each new task. This ensures that each branch is based on the most up-to-date version of the main codebase. Once your PR is merged into the main branch, start a new branch for the next task, rather than branching off from previous task branches.

Implement pagination for the movie list if it exceeds the screen space.

The input field should allow users to start typing and focus automatically by pressing the "/" key to enhance the user experience.

Ensure that the search query is reflected in the URL as query parameters.

Implement debouncing on the search input to prevent excessive API calls as the user types.

Display a loading spinner while the search request is being processed.

If a movie does not return an image, provide a fallback image.

Display error responses like Too many results or Movie not found from the OMDb API in a toastr.