fix: camel case on msg

[evilpeach]

Fix CFE-602

Summary by CodeRabbit

• Bug Fixes

  • Improved camel case formatting in messages for better consistency and readability.
  • Addressed various transaction rendering and alignment issues.

• Enhancements

  • Updated transformation logic for transaction schemas to preserve critical properties during data processing.
  • Adjusted transaction response handling to maintain original data structure.

[linear]

CFE-602 [Fix] `camelToSnake` in tx details

[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	Sep 16, 2024 3:11am

6 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
celatone-frontend-main	⬜️ Ignored (Inspect)	Visit Preview		Sep 16, 2024 3:11am
initia-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Sep 16, 2024 3:11am
neutron-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Sep 16, 2024 3:11am
osmosis-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Sep 16, 2024 3:11am
sei-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Sep 16, 2024 3:11am
terra-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Sep 16, 2024 3:11am

[coderabbitai]

Walkthrough

The recent updates involve modifications to the CHANGELOG.md, adjustments in the useTxData function within the src/lib/services/tx/index.ts file, and enhancements to Zod schemas in src/lib/services/types/tx.ts. The CHANGELOG.md now includes a bug fix entry, while the useTxData function no longer converts the txResponse object to camelCase. Additionally, the Zod schemas have been updated to retain specific properties from the original input during transformation.

Changes

File	Change Summary
CHANGELOG.md	Added a bug fix entry addressing issue #1149 for camel case formatting.
src/lib/services/tx/index.ts	Removed snakeToCamel utility function call in useTxData, preserving original txResponse format.
src/lib/services/types/tx.ts	Enhanced Zod schemas (zTxBody, zTx, zTxResponse) to retain specific properties during transformation.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant TxService
    participant ZodSchemas

    User->>App: Request transaction data
    App->>TxService: Call useTxData
    TxService->>TxService: Retrieve txResponse
    TxService-->>App: Return txResponse (unchanged format)
    App->>ZodSchemas: Validate txResponse
    ZodSchemas-->>App: Return validated data with retained properties
    App-->>User: Display transaction data

Loading

🐰 In the code we hop and play,
Fixing bugs along the way.
With schemas bright and data clear,
Our code now sings, oh so dear!
A leap of joy, we celebrate,
For every change, we elevate! 🌟

Possibly related PRs

• fix: duplicate contracts evm txs #1152: The changes in the CHANGELOG.md file of the main PR relate to bug fixes, which aligns with the bug fix focus of PR fix: duplicate contracts evm txs #1152 that addresses issues in transaction data integrity.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1863ba1 and 0c069a9.

Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• src/lib/services/tx/index.ts (1 hunks)

Files skipped from review due to trivial changes (1)

• CHANGELOG.md

Files skipped from review as they are similar to previous changes (1)

• src/lib/services/tx/index.ts

---

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 generate interesting stats about this repository and render them as a table.
  -- @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.