Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fix loading contracts using code_id in query params #1236

Merged
merged 4 commits into from
May 21, 2024

Conversation

Hemanthghs
Copy link
Collaborator

@Hemanthghs Hemanthghs commented May 14, 2024

Summary by CodeRabbit

  • New Features
    • URL parameter code_id now sets the selected tab to 'All Contracts' automatically, enhancing navigation efficiency.

Copy link

vercel bot commented May 14, 2024

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

Name Status Preview Comments Updated (UTC)
resolute ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 21, 2024 6:07am

Copy link
Contributor

coderabbitai bot commented May 14, 2024

Walkthrough

The frontend underwent a significant update where the PageContracts.tsx file now incorporates a new variable, paramsCodeId, to fetch the code_id query parameter from the URL. This addition triggers a useEffect hook to automatically switch the selected tab to 'All Contracts' when code_id is present in the URL parameters, enhancing user navigation based on URL queries.

Changes

File Path Change Summary
frontend/src/app/(routes)/cosmwasm/[network]/PageContracts.tsx Updated to include paramsCodeId for fetching code_id from the URL, activating a useEffect to set the selected tab to 'All Contracts'.
frontend/src/app/(routes)/cosmwasm/components/AddAddresses.tsx Fixed logic issue in AddAddresses.tsx where input.trim() now correctly returns the trimmed input value.

In code we trust, with bytes that weave,
A change so small, yet webs we cleave.
Parameters guide, to tabs we roam,
A rabbit's touch, to bring us home. 🐇✨


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
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between c1939db and f953a2e.
Files selected for processing (1)
  • frontend/src/app/(routes)/cosmwasm/[network]/PageContracts.tsx (1 hunks)
Additional comments not posted (2)
frontend/src/app/(routes)/cosmwasm/[network]/PageContracts.tsx (2)

22-22: The introduction of paramsCodeId to capture the code_id query parameter is correct and follows best practices.


30-34: The useEffect hook correctly updates the selected tab to 'All Contracts' when paramsCodeId is present. Ensure that the dependency array [paramsCodeId] is accurate and only triggers when paramsCodeId changes.

Verification successful

The useEffect hook in PageContracts.tsx correctly updates the selected tab to 'All Contracts' when paramsCodeId is present and has the appropriate dependency array [paramsCodeId]. This ensures that the effect only triggers when paramsCodeId changes.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the dependency array for the useEffect hook is accurate and only triggers when `paramsCodeId` changes.

# Test: Search for the useEffect hook with `paramsCodeId` in the dependency array. Expect: Only occurances with correct dependency array.
rg --type js --type ts $'useEffect(() => {\n    if (paramsCodeId?.length) {\n      setSelectedTab(\'All Contracts\');\n    }\n  }, [paramsCodeId]);'

Length of output: 522



Script:

#!/bin/bash
# Description: Verify that the dependency array for the useEffect hook is accurate and only triggers when `paramsCodeId` changes.

# Test: Search for the useEffect hook with `paramsCodeId` in the dependency array. Expect: Only occurrences with correct dependency array.
rg --type js --type ts 'useEffect\(\(\) => \{\s+if \(paramsCodeId\?\.\length\) \{\s+setSelectedTab\('\'All Contracts\'\);\s+\}\s+\}, \[paramsCodeId\]\);'

Length of output: 93



Script:

#!/bin/bash
# Description: Verify that the dependency array for the useEffect hook is accurate and only triggers when `paramsCodeId` changes.

# Test: Search for the useEffect hook with `paramsCodeId` in the dependency array. Expect: Only occurrences with correct dependency array.
rg --type js --type ts 'useEffect\(\(\) => \{\s+if \(paramsCodeId\?\.\length\) \{\s+setSelectedTab\("All Contracts"\);\s+\}\s+\}, \[paramsCodeId\]\);'

Length of output: 389



Script:

#!/bin/bash
# Description: Verify that the dependency array for the useEffect hook is accurate and only triggers when `paramsCodeId` changes.

# Test: Search for the useEffect hook with `paramsCodeId` in the dependency array. Expect: Only occurrences with correct dependency array.
rg --type js --type ts 'useEffect\(.*\[paramsCodeId\]\);'

Length of output: 59



Script:

#!/bin/bash
# Description: Search for all useEffect hooks and manually inspect those involving `paramsCodeId`.

# Test: Search for all useEffect hooks.
rg --type js --type ts 'useEffect\('

Length of output: 13555



Script:

#!/bin/bash
# Description: Extract the useEffect hook from PageContracts.tsx to verify the dependency array.

# Test: Extract the useEffect hook from PageContracts.tsx.
rg --type js --type ts -A 5 'useEffect\(' frontend/src/app/\(routes\)/cosmwasm/\[network\]/PageContracts.tsx

Length of output: 360

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between f953a2e and abe3fb5.
Files selected for processing (1)
  • frontend/src/app/(routes)/cosmwasm/components/AddAddresses.tsx (1 hunks)
Files skipped from review due to trivial changes (1)
  • frontend/src/app/(routes)/cosmwasm/components/AddAddresses.tsx

@charymalloju charymalloju merged commit 673123a into master May 21, 2024
9 checks passed
@charymalloju charymalloju deleted the hemanth/cosmwasm-fixes branch May 21, 2024 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants