Skip to content

Conversation

@vicb
Copy link
Contributor

@vicb vicb commented Jan 23, 2025

based on the Python example

Summary by CodeRabbit

  • Documentation
    • Enhanced JavaScript API documentation for ast-grep.
    • Added installation instructions for @ast-grep/napi.
    • Introduced detailed explanations of SgRoot and SgNode classes.
    • Added examples demonstrating the use of NapiConfig, node traversal, and code fixing techniques.
    • Clarified usage of new methods: replace and commitEdits.

@coderabbitai
Copy link

coderabbitai bot commented Jan 23, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request enhances the JavaScript API documentation for ast-grep, focusing on the website/guide/api-usage/js-api.md file. The update introduces comprehensive installation instructions for the @ast-grep/napi package, adds detailed explanations of core classes like SgRoot and SgNode, and provides new examples demonstrating API usage. The documentation now includes more in-depth guidance on node traversal, finding nodes with specific constraints, and code editing capabilities.

Changes

File Change Summary
website/guide/api-usage/js-api.md - Added installation instructions for npm and pnpm
- Introduced detailed explanations of SgRoot and SgNode classes
- Added new example with NapiConfig for node finding
- Included section on code fixing with replace method
- Added new methods: replace(text: string): Edit, commitEdits(edits: Edit[]): string, and new interface Edit

Sequence Diagram

sequenceDiagram
    participant User
    participant SgNode
    participant Edit
    
    User->>SgNode: find nodes
    SgNode-->>User: return matching nodes
    User->>SgNode: replace(text)
    SgNode->>Edit: create Edit
    User->>SgNode: commitEdits(edits)
    SgNode-->>User: return modified code
Loading

Poem

🐰 Ast-grep's JavaScript dance,
Nodes hopping with elegant stance,
Replace and commit with glee,
Code transformation, wild and free!
A rabbit's API delight! 🌟


📜 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 f2a0115 and d34af80.

📒 Files selected for processing (1)
  • website/guide/api-usage/js-api.md (3 hunks)

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

Copy link

@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

🧹 Nitpick comments (2)
website/guide/api-usage/js-api.md (2)

14-22: Consider adding yarn installation instructions.

The installation section nicely uses code groups to show npm and pnpm commands. Consider adding yarn for completeness:

 ::: code-group
 
 ```bash[npm]
 npm install --save @ast-grep/napi
pnpm add @ast-grep/napi

+bash[yarn] +yarn add @ast-grep/napi +

:::


---

`139-148`: **Add explanation for the constraints object.**

While the example demonstrates `NapiConfig` usage, it would be helpful to explain:
1. The purpose and structure of the `constraints` object
2. Available constraint types besides `regex`
3. How the constraint `{ regex: "hello" }` affects the pattern matching


Consider adding a brief explanation before the example:
```diff
+// The constraints object allows you to add additional matching criteria
+// for meta variables. In this example, we ensure that the argument ($A)
+// contains the word "hello" using a regex constraint.
 const node = root.find({
   rule: {
     pattern: "console.log($A)",
   },
   constraints: {
     A: { regex: "hello" }
   }
 });
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e3e1265 and f2a0115.

📒 Files selected for processing (1)
  • website/guide/api-usage/js-api.md (3 hunks)
🔇 Additional comments (1)
website/guide/api-usage/js-api.md (1)

30-30: Great addition of core concepts!

The clear listing of main classes and the jQuery analogy make the API more approachable for JavaScript developers.

Copy link
Member

@HerringtonDarkholme HerringtonDarkholme left a comment

Choose a reason for hiding this comment

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

thanks!

@HerringtonDarkholme HerringtonDarkholme added this pull request to the merge queue Jan 23, 2025
Merged via the queue into ast-grep:main with commit cef0d2c Jan 23, 2025
1 check was pending
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