Fix search history consistency issue

[Recxsmacx]

Fixes #3676

Update search functionality to make search history consistent between search bar and search icon.

• Update AlgoliaModal component in components/AlgoliaSearch.tsx to use INDEX_NAME for both search placeholders and index name.
• Update SearchButton component in components/navigation/DocsNavWrapper.tsx to use INDEX_NAME for searching resources.
• Update SearchButton component in components/navigation/DocsMobileMenu.tsx to use INDEX_NAME for searching resources.
• Update SearchButton component in components/navigation/NavBar.tsx to use INDEX_NAME for searching resources.
• Update SearchButton component in components/navigation/MobileNavMenu.tsx to use INDEX_NAME for searching resources.

Summary by CodeRabbit

• New Features
  • The search input now displays a clear, static message for easier discovery.
  • A unified search configuration has been applied across navigation interfaces, ensuring a consistent experience on both mobile and desktop.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request centralizes the search index configuration across components. In the AlgoliaSearch component, the AlgoliaModal now uses a static placeholder ("Search resources") and a constant INDEX_NAME instead of a dynamic value. Simultaneously, navigation components update their import statements and usage, replacing DOCS_INDEX_NAME with INDEX_NAME for the SearchButton component. Overall, the functional flow remains unchanged.

Changes

File(s)	Change Summary
components/AlgoliaSearch.tsx	Updated AlgoliaModal: replaced a conditional placeholder with a static "Search resources" and changed the dynamic indexName to the constant INDEX_NAME.
components/navigation/DocsMobileMenu.tsx, components/navigation/DocsNavWrapper.tsx, components/navigation/MobileNavMenu.tsx, components/navigation/NavBar.tsx	Replaced DOCS_INDEX_NAME with INDEX_NAME in import statements and when passing the indexName prop to the SearchButton component; added INDEX_NAME import where necessary.

Possibly related PRs

• Fix search history consistency #3680: Updated the indexName property in the SearchButton component to utilize the constant INDEX_NAME.
• fix: address search bar issue in the navbar #3447: Adjusted the SearchButton’s handling of its children prop, connected through the updated index name usage.
• fix: remove hydration errors #3262: Made similar modifications to the indexName constant across different files affecting the SearchButton component.

Suggested labels

ready-to-merge

Suggested reviewers

• derberg
• magicmatatjahu
• devilkiller-ag
• akshatnema
• sambhavgupta0705
• anshgoyalevil
• asyncapi-bot-eve
• Mayaleeeee
• TRohit20

Poem

I'm a bunny on a coding spree,
Hopping through changes light and free,
Static placeholders now lead the way,
With INDEX_NAME guiding the search each day,
No more twists in our navigation run—
Carrots and code make a perfect fun!
🐇🥕 Happy hops in every line!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b1c7f7c and d4fd2e4.

📒 Files selected for processing (5)

• components/AlgoliaSearch.tsx (1 hunks)
• components/navigation/DocsMobileMenu.tsx (2 hunks)
• components/navigation/DocsNavWrapper.tsx (2 hunks)
• components/navigation/MobileNavMenu.tsx (2 hunks)
• components/navigation/NavBar.tsx (3 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[asyncapi-bot]

We require all PRs to follow Conventional Commits specification.
More details 👇🏼

 No release type found in pull request title "Fix search history consistency issue". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	d4fd2e4
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67b46c23a8608b0008ae9c81
😎 Deploy Preview	https://deploy-preview-3703--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.