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

chore: remove @zetachain/addresses from package.json #177

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

fadeev
Copy link
Member

@fadeev fadeev commented Aug 31, 2024

It's not being used anywhere, so we should remove this package.

Summary by CodeRabbit

  • Chores
    • Removed the dependency on @zetachain/addresses, streamlining project dependencies.
    • Minor formatting change for improved file standards.

@fadeev fadeev requested review from andresaiello and a team as code owners August 31, 2024 01:28
Copy link
Contributor

coderabbitai bot commented Aug 31, 2024

Walkthrough

Walkthrough

The primary change involves the removal of the dependency @zetachain/addresses version ^0.0.10 from the package.json file. This indicates a modification in the project's dependency management, reflecting a potential shift in required functionalities. Additionally, a minor formatting adjustment was made by removing a newline character at the end of the file.

Changes

File Change Summary
package.json Removed dependency @zetachain/addresses version ^0.0.10; minor formatting change (newline removal).

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

@fadeev fadeev changed the title chore: remove zetachain addresses from package.json chore: remove zetachain addresses from package.json Aug 31, 2024
@fadeev fadeev changed the title chore: remove zetachain addresses from package.json chore: remove @zetachain/addresses from package.json Aug 31, 2024
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 d68cf4a and 6bcaf83.

Files selected for processing (1)
  • package.json (2 hunks)
Files skipped from review due to trivial changes (1)
  • package.json

@fadeev
Copy link
Member Author

fadeev commented Sep 9, 2024

@andresaiello @zeta-chain/fullstack please, review.

@fadeev fadeev merged commit 7139675 into main Sep 10, 2024
5 checks passed
@fadeev fadeev deleted the remove-zetachain-addresses-from-package-json branch September 10, 2024 13:10
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