Skip to content

Update README.md - #185

Merged
IAmKio merged 5 commits into
masterfrom
improve/readme-update
Jul 17, 2025
Merged

Update README.md#185
IAmKio merged 5 commits into
masterfrom
improve/readme-update

Conversation

@IAmKio

@IAmKio IAmKio commented Jul 17, 2025

Copy link
Copy Markdown
Collaborator

Description

  • Updated: Brand new readme!

How Has This Been Tested?

  • Locally

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Summary by CodeRabbit

  • Documentation
    • Completely rewrote and expanded the README to provide a comprehensive, framework-agnostic introduction and user guide for TransactionKit.
    • Added detailed installation instructions, quick start examples, API usage, configuration options, and method overviews.
    • Included sections on contributing, security, support resources, and community links for improved user engagement.

@IAmKio
IAmKio requested a review from RanaBug July 17, 2025 15:37
@IAmKio IAmKio self-assigned this Jul 17, 2025
@coderabbitai

coderabbitai Bot commented Jul 17, 2025

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@IAmKio has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 50 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 0e67f10 and c984a0e.

📒 Files selected for processing (1)
  • README.md (1 hunks)

Walkthrough

The README.md file was completely rewritten and expanded. The new version provides a comprehensive, framework-agnostic guide to TransactionKit, including installation, usage, API documentation, configuration, and community resources. The package version was also updated from 2.0.0 to 2.0.1. No changes were made to code or exported entities; only documentation and version metadata were updated.

Changes

File(s) Change Summary
README.md Rewritten and expanded from a minimal description to a detailed, user-friendly guide and reference
CHANGELOG.md Added new entry for version 2.0.1 documenting README rewrite and enhancements
package.json Package version updated from 2.0.0 to 2.0.1; no other changes to dependencies or scripts

Poem

In the warren, README grew anew,
With guides and tips for all to view.
From React roots to frameworks wide,
TransactionKit’s secrets no longer hide.
Now every bunny, near or far,
Can hop through docs and raise the bar! 🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@github-actions

Copy link
Copy Markdown

Yooo! You forgot to bump the version in package.json!

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
README.md (4)

31-40: Add peer-dependency installation hints

The quick-start snippet relies on viem and viem/accounts, yet the installation section only shows @etherspot/transaction-kit.

 ## 📦 Installation
 ...
 # Using npm
 npm install @etherspot/transaction-kit
+# Peer deps (needed for the examples below)
+npm install viem viem/accounts

Documenting the peer deps prevents “module not found” surprises for new users.


54-60: Clarify runtime context & avoid window.ethereum! non-null assertion

The snippet mixes browser-specific globals (window.ethereum) with a private-key wallet, which is more typical of Node scripts. Consider:

  1. Explaining that this example targets the browser and requires an injected wallet (e.g. MetaMask).
  2. Removing the non-null assertion or guarding against its absence to prevent runtime errors:
-  transport: custom(window.ethereum!),
+  transport: typeof window !== 'undefined' && window.ethereum
+    ? custom(window.ethereum)
+    : /* fallback transport here */,

Explicitly stating the expected environment keeps the example copy-paste-safe.


55-55: Discourage hard-coding private keys in documentation

Even in examples, hard-coding a raw private key encourages bad security practices. Recommend showing environment-variable usage instead:

-const account = privateKeyToAccount('0x...your-private-key...');
+const account = privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`);

This small change nudges readers toward safer habits.


227-229: Resolve markdown-lint issue MD036 (emphasis as heading)

Using emphasis for “Made with ❤️ …” and the closing line violates markdown-lint MD036 and slightly hurts accessibility. Convert them to plain text or proper headings:

-**Made with ❤️ by the Etherspot team**
-
-_Now go forth and build amazing things! The blockchain is your oyster! 🦪_
+### Made with ❤️ by the Etherspot team
+
+Now go forth and build amazing things — the blockchain is your oyster! 🦪

Also trims excessive exclamation marks flagged by LanguageTool.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b7520b0 and d303619.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[style] ~229-~229: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...herspot team** _Now go forth and build amazing things! The blockchain is your oyster! ...

(AWESOME)


[style] ~229-~229: Using many exclamation marks might seem excessive (in this case: 9 exclamation marks for a text that’s 2917 characters long)
Context: ...ng things! The blockchain is your oyster! 🦪_

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.17.2)
README.md

227-227: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


229-229: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

Comment thread README.md
- `getWalletAddress()` - Get your wallet address
- `getState()` - Get current kit state
- `setDebugMode()` - Enable/disable debug logging
- `reset()` - Clear all transactions and batches

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

a few methods missing:

  • getProvider()
  • getSdk()
  • remove()
  • update()

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Added ✅

RanaBug
RanaBug previously approved these changes Jul 17, 2025
@IAmKio
IAmKio merged commit 49542dd into master Jul 17, 2025
5 checks passed
@IAmKio
IAmKio deleted the improve/readme-update branch July 17, 2025 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants