fix (cosmwasm): update get txn endpoints

[Hemanthghs]

Summary by CodeRabbit

• New Features

  • Introduced a copyable codeId component in the transaction status dialogs, enhancing user experience by allowing easy copying when available.
  • Improved URL construction for transaction requests to include chain ID, ensuring more accurate transaction fetching.

• Bug Fixes

  • Minor formatting improvements for better code readability, though no functional changes were made.

[vercel]

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	Sep 21, 2024 9:43am

[coderabbitai]

Walkthrough

The changes introduced in this pull request involve enhancements to the user interface by implementing conditional rendering of a Copy component in two dialog components, DialogTxInstantiateStatus and DialogTxUploadCodeStatus. The rendering of this component depends on the presence of txResponse?.codeId. Additionally, a utility function, addChainIDParam, is added to the cosmwasmSlice.ts file to improve URL construction for transaction requests by including the chain ID parameter.

Changes

File	Change Summary
frontend/src/app/(routes)/cosmwasm/components/tx-status/DialogTxInstantiateStatus.tsx frontend/src/app/(routes)/cosmwasm/components/tx-status/DialogTxUploadCodeStatus.tsx	Introduced conditional rendering of a Copy component based on txResponse?.codeId. If present, it is rendered; otherwise, nothing is displayed.
frontend/src/store/features/cosmwasm/cosmwasmSlice.ts	Added a utility function addChainIDParam for improved URL construction in transaction requests, including the chain ID parameter. Minor formatting changes were also made.

Possibly related PRs

• feat: add view all contracts #1235: The changes in the main PR involve conditional rendering of a Copy component based on txResponse?.codeId, which is relevant to the CodeItem component introduced in the retrieved PR, as it also deals with code IDs and their display.

Poem

In the garden where code blooms bright,
A Copy component shines with delight.
With txResponse in hand, we cheer,
For now, code IDs are crystal clear!
Hopping through changes, we dance and play,
Celebrating improvements, hip-hip-hooray! 🐇✨

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d50a50e and b51271d.

Files selected for processing (3)

• frontend/src/app/(routes)/cosmwasm/components/tx-status/DialogTxInstantiateStatus.tsx (1 hunks)
• frontend/src/app/(routes)/cosmwasm/components/tx-status/DialogTxUploadCodeStatus.tsx (1 hunks)
• frontend/src/store/features/cosmwasm/cosmwasmSlice.ts (4 hunks)

Additional comments not posted (7)

frontend/src/app/(routes)/cosmwasm/components/tx-status/DialogTxUploadCodeStatus.tsx (1)

75-77: LGTM!

The conditional rendering of the Copy component based on the availability of txResponse?.codeId is implemented correctly. This change enhances the user interface by providing a copyable version of the code ID when it is available.

frontend/src/app/(routes)/cosmwasm/components/tx-status/DialogTxInstantiateStatus.tsx (1)

76-78: LGTM!

The conditional rendering of the Copy component based on the availability of txResponse?.codeId is implemented correctly. This change enhances the user experience by providing a convenient way to copy the code ID when it is available.

frontend/src/store/features/cosmwasm/cosmwasmSlice.ts (5)

9-9: LGTM!

The import statement looks good. The imported utility functions are likely used in the subsequent code changes.

---

229-233: LGTM!

The changes to the transaction URL construction look good. Using the addChainIDParam utility function to include the chain ID parameter is a nice improvement for multi-chain support.

---

Line range hint 242-246: LGTM!

Tracking the success or failure of contract execution using the trackEvent function is a good addition for monitoring and analytics purposes. The use of the code value to determine the execution status is appropriate.

---

270-274: LGTM!

The changes to the transaction URL construction in the uploadCode function are consistent with the previous changes in the executeContract function. Using the addChainIDParam utility function to include the chain ID parameter is a nice improvement for multi-chain support.

---

318-322: LGTM!

The changes to the transaction URL construction in the txInstantiateContract function are consistent with the previous changes in the executeContract and uploadCode functions. Using the addChainIDParam utility function to include the chain ID parameter is a nice improvement for multi-chain support.

---

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