feat: support move/ prefix in search

[evilpeach]

Summary by CodeRabbit

• New Features
  • Extended search functionality to recognize and process "move/" prefixed hex module addresses, enabling broader address query support in the app.

https://rest.initiation-2.initia.xyz/initia/mstaking/v1/params

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
celatone-frontend-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2025 3:41am

6 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
celatone-frontend-main	⬜️ Ignored (Inspect)			Feb 13, 2025 3:41am
initia-celatone-frontend	⬜️ Ignored (Inspect)			Feb 13, 2025 3:41am
neutron-celatone-frontend	⬜️ Ignored (Inspect)			Feb 13, 2025 3:41am
osmosis-celatone-frontend	⬜️ Ignored (Inspect)			Feb 13, 2025 3:41am
sei-celatone-frontend	⬜️ Ignored (Inspect)			Feb 13, 2025 3:41am
terra-celatone-frontend	⬜️ Ignored (Inspect)			Feb 13, 2025 3:41am

[coderabbitai]

Walkthrough

This pull request introduces support for "move/" prefixed hex module addresses in the search functionality. A new validation function, isMovePrefixHexModuleAddress, is added to the utility module, and the search handler is updated to use this function. Additionally, the CHANGELOG file is updated with an entry for this new feature, linked to pull request #1233. The changes maintain the existing structure and logic while expanding the address handling capabilities.

Changes

File(s)	Change Summary
CHANGELOG.md	Added a new feature entry for supporting "move/" prefixed hex module addresses in the search functionality, with a reference to PR #1233 in the "Unreleased" section.
src/lib/services/searchService.ts, src/lib/utils/validate.ts	Introduced the isMovePrefixHexModuleAddress utility function; updated the search handler to detect "move/" prefixed addresses and append a corresponding result when matched.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant SearchHandler
    participant ValidationUtil

    User->>SearchHandler: Enter search keyword
    SearchHandler->>ValidationUtil: isMovePrefixHexModuleAddress(keyword)
    ValidationUtil-->>SearchHandler: Returns true/false
    alt Valid "move/" prefix address
        SearchHandler->>SearchHandler: Slice keyword to form valid address
        SearchHandler->>User: Return result with type "Account Address"
    else Not valid
        SearchHandler->>User: Continue with normal search flow
    end

Loading

Possibly related PRs

• Fix/contract address validation #1192: Introduces address validation functions in the utility module, focusing on similar logic to the new isMovePrefixHexModuleAddress function.

Poem

I'm a rabbit with a coding zest,
Hoping through "move/" paths with my best.
My ears twitch to each new byte,
As hex addresses now shine bright.
I leap through code in playful delight!
🐰💻
Happy hops in every line!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ac1732 and 2658404.

📒 Files selected for processing (3)

• CHANGELOG.md (1 hunks)
• src/lib/services/searchService.ts (3 hunks)
• src/lib/utils/validate.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (javascript)

🔇 Additional comments (4)

src/lib/utils/validate.ts (1)

60-63: LGTM! Clean implementation of Move prefix hex module address validation.

The function follows the established pattern of other validation functions and correctly validates the format using regex.

src/lib/services/searchService.ts (2)

123-128: LGTM! Clean implementation of Move prefix hex module address search support.

The code properly handles Move prefix addresses by:

1. Checking if Move is enabled
2. Validating the address format
3. Transforming the address from "move/" prefix to "0x" prefix

---

373-379: LGTM! Proper integration with search results.

The code correctly adds the transformed address to the search results with appropriate type.

CHANGELOG.md (1)

42-42: LGTM! Clear and well-formatted changelog entry.

The entry properly documents the new feature and links to the PR.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.