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

Examples.md: added more examples #59

Merged
merged 2 commits into from
Jan 17, 2025
Merged

Examples.md: added more examples #59

merged 2 commits into from
Jan 17, 2025

Conversation

niklak
Copy link
Owner

@niklak niklak commented Jan 17, 2025

Summary by CodeRabbit

  • Documentation

    • Added examples for retrieving document base URI
    • Added examples for verifying selection and node matches
    • Added examples for finding child elements efficiently
  • Chores

    • Updated export order in entities
    • Minor comment correction in test file

Copy link

coderabbitai bot commented Jan 17, 2025

Walkthrough

This pull request introduces new methods and documentation for the dom_query library. The changes include adding base_uri(), is(), and find() methods to the Document, Selection, and NodeRef classes. The documentation in Examples.md and README.md has been updated to provide practical examples of these new functionalities, demonstrating how to retrieve base URIs, verify node selections, and efficiently find child elements.

Changes

File Change Summary
Examples.md Added sections demonstrating new library methods for base URI retrieval, selection verification, and child element finding
README.md Expanded "Examples" section with detailed use cases for new base_uri(), is(), and find() methods
src/entities.rs Reordered public exports of InnerHashMap and InnerHashSet
tests/node-traversal.rs Minor comment text modification and added closing brace

Possibly related PRs

Poem

🐰 In the DOM's vast, tangled tree,
New methods hop with glee!
Base URIs found with grace,
Selections matched with playful pace.
Code queries dance, swift and light,
A rabbit's coding delight! 🌟


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

codecov bot commented Jan 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.85%. Comparing base (ef8facd) to head (1b1759b).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #59   +/-   ##
=======================================
  Coverage   91.85%   91.85%           
=======================================
  Files          15       15           
  Lines        2577     2577           
=======================================
  Hits         2367     2367           
  Misses        210      210           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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: 1

🧹 Nitpick comments (1)
Examples.md (1)

726-758: Consider adding error handling examples.

The example effectively demonstrates the find() method usage. However, it would be beneficial to show how the method handles invalid paths (e.g., paths that start before the current node).

Consider adding an example that demonstrates error handling:

// This will fail as the path starts before the current node
let invalid_path = &["html", "body", "div", "a"];
assert!(main_node.find(invalid_path).is_empty());

// This will work as the path starts after the current node
let valid_path = &["div", "a"];
assert_eq!(main_node.find(valid_path).len(), total_links);
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ef8facd and 18497f3.

📒 Files selected for processing (4)
  • Examples.md (1 hunks)
  • README.md (1 hunks)
  • src/entities.rs (1 hunks)
  • tests/node-traversal.rs (2 hunks)
✅ Files skipped from review due to trivial changes (2)
  • tests/node-traversal.rs
  • src/entities.rs
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: test
🔇 Additional comments (3)
Examples.md (2)

646-682: LGTM! Clear and comprehensive example.

The example effectively demonstrates the base_uri() method usage at both document and node level, with helpful comments explaining the implementation details and performance considerations.


685-723: LGTM! Well-structured example with clear explanations.

The example effectively demonstrates the versatility of the is() method for both Selection and NodeRef, with clear comments explaining the differences and use cases.

README.md (1)

666-779: LGTM! Documentation is consistent across files.

The examples in README.md perfectly mirror those in Examples.md, maintaining consistency in the documentation. This is excellent for user experience as it provides multiple entry points to learn about the new features.

Examples.md Outdated
</head>
<body>
<div id="main"></div>
</div>
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix the typo: Remove extra closing div tag.

There's an extra closing </div> tag that should be removed.

-        </div>

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 (3)
Examples.md (3)

646-681: Add error handling examples for base_uri().

The example demonstrates successful cases but doesn't show how to handle cases where the base URI is missing. Consider adding examples that demonstrate:

  1. Error handling when no base element exists
  2. Handling malformed href attributes
// Example: Error handling
let doc = Document::from("<html><head></head></html>");
assert!(doc.base_uri().is_none());  // No base element

let doc = Document::from(r#"<html><head><base href="invalid://uri"/></head></html>"#);
if let Some(uri) = doc.base_uri() {
    println!("Base URI: {}", uri);
} else {
    println!("No valid base URI found");
}

684-722: Enhance selector examples for is() method.

The example could be enriched with more complex selector patterns to better demonstrate the method's capabilities:

// Example: Complex selectors
assert!(main_sel.is("div#main:not(.hidden)[dir]"));
assert!(main_node.is("html > body > div#main:first-child:not(:empty)"));

// Example: Combining multiple checks
assert!(main_sel.is("div#main") && main_sel.is("[dir=ltr]"));

725-757: Add performance comparison and more path patterns.

The example could be enhanced with:

  1. Performance comparison between find() and select()
  2. More examples of valid and invalid path patterns
// Example: Performance comparison
let start = std::time::Instant::now();
let found_links = main_node.find(&["div", "a"]);
println!("find() took: {:?}", start.elapsed());

let start = std::time::Instant::now();
let selected_links = doc.select("#main div a");
println!("select() took: {:?}", start.elapsed());

// Example: More path patterns
main_node.find(&["div"]);  // Direct children
main_node.find(&["div", "*"]);  // Any element under div
main_node.find(&["div[class]", "a"]);  // Elements with attributes
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 18497f3 and 1b1759b.

📒 Files selected for processing (2)
  • Examples.md (1 hunks)
  • README.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: test-wasm
  • GitHub Check: test
🔇 Additional comments (1)
README.md (1)

666-778: LGTM! Examples are consistent with Examples.md.

The examples in README.md match those in Examples.md, providing consistent documentation across the repository.

@niklak niklak merged commit 473fc5a into main Jan 17, 2025
9 checks passed
@niklak niklak deleted the feature/more-examples branch January 17, 2025 12:34
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.

1 participant