style: fix lint

[ALPAC-4]

Summary by CodeRabbit

• New Features

  • Added an HTTP endpoint to retrieve consensus state data with timestamp and proof details.

• Refactor

  • Streamlined test operations by simplifying error handling and shifting from asynchronous to synchronous execution.

• Chore

  • Refined internal configuration for testing consistency and removed legacy blockchain packet receipt functionality.

[coderabbitai]

Walkthrough

The pull request transitions the Jest configuration from CommonJS to ES module exports. The client controller test has been updated to execute side effects without asynchronous handling by removing the async keyword. The file handling blockchain packet messages has been removed entirely. In addition, error handling in two HTTP GET request handlers has been simplified within the test setup file, and a new GET endpoint for consensus state retrieval has been added. All changes focus on refactoring export styles, modifying test behavior, and extending HTTP API capabilities.

Changes

File(s)	Change Summary
jest.config.js	Transitioned from using module.exports to individual named ES module exports for configuration properties (preset, setupFilesAfterEnv, testEnvironment, testMatch, moduleNameMapper, maxWorkers).
src/db/controller/client.spec.ts	Modified test setup: adjusted mockServers invocation for side effects and changed the test function from asynchronous to synchronous execution.
src/msgs/recvPacet.ts	Removed file that generated blockchain packet messages, including helper functions for generating proofs and constructing MsgRecvPacket.
src/test/testSetup.ts	Simplified error handling in two existing HTTP GET request handlers by removing unused error parameter, and added a new GET endpoint (/ibc/core/client/v1/consensus_states/:clientId/revision/0/height/0) to return mock consensus state data.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    Client->>Server: GET /ibc/core/client/v1/consensus_states/:clientId/revision/0/height/0
    Server->>Server: Process the request and prepare mock consensus state data
    Server-->>Client: JSON response with consensus state data (timestamp, proof structure)

Loading

Poem

I'm a little rabbit with a hop so light,
Watching code changes bring new delight.
Configs now export with modern style,
Tests run swift with a synchronous smile.
Endpoints bloom with responses so clear,
I nibble on updates and cheer with heart so dear!
🐰🌟

---

📜 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 1246caf and 642d101.

📒 Files selected for processing (4)

• jest.config.js (1 hunks)
• src/db/controller/client.spec.ts (1 hunks)
• src/msgs/recvPacet.ts (0 hunks)
• src/test/testSetup.ts (3 hunks)

💤 Files with no reviewable changes (1)

• src/msgs/recvPacet.ts

🔇 Additional comments (5)

src/db/controller/client.spec.ts (2)

8-8: LGTM! Good use of void operator.

The void operator explicitly indicates the intent to execute mockServers for its side effects while ignoring its return value, which is a good TypeScript pattern.

---

9-9: LGTM! Appropriate removal of async.

Removing the async keyword is correct since there are no await calls in the test function.

jest.config.js (1)

2-9: LGTM! Good modernization to ES modules.

Converting from CommonJS to ES module exports is a good modernization that aligns with current JavaScript best practices.

src/test/testSetup.ts (2)

64-64: LGTM! Good cleanup of unused error parameters.

Removing unused error parameters in catch blocks improves code cleanliness and satisfies common linting rules.

Also applies to: 83-83

---

92-116: LGTM! Well-structured mock endpoint.

The new consensus state mock endpoint follows consistent patterns with existing endpoints and provides appropriate mock data structure.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

[joon9823]

LGTM