chore: add some utils for testing

[morgante]

Expose some more useful test utils.

Summary by CodeRabbit

• New Features

  • Added a new function for testing purposes in the pattern compiler, enhancing flexibility in behavior based on user inputs.
  • Introduced a method to construct a context in the problem-solving module, aiding in more robust testing scenarios.

• Enhancements

  • Enhanced the pattern building process with a conditional behavior to wrap patterns automatically based on user settings.

• Refactor

  • Modified a conditional compilation attribute to include testing scenarios, ensuring broader testing coverage and functionality verification.

• Documentation

  • No visible changes to documentation for end-users.

• Bug Fixes

  • No specific bug fixes affecting end-users directly.

• Tests

  • New testing functionalities added across various modules to ensure reliability and performance.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates across various crates primarily enhance testing capabilities and refine functionality. Key changes include making functions public for broader access, adding new parameters and methods to existing functions for conditional behaviors, and modifying compilation attributes to include additional features. These modifications aim to improve the flexibility and testability of the system, ensuring more robust and adaptable codebases.

Changes

File	Changes
.../auth/src/testing.rs	Made get_config_var public.
.../core/src/pattern_compiler/builder.rs .../core/src/pattern_compiler/compiler.rs	Added new parameters and methods for conditional behaviors and testing.
.../core/src/problem.rs	Added get_context for testing context construction.
.../grit-util/src/analysis_logs.rs	Added methods to initialize AnalysisLogs and implemented Default trait.
.../util/src/runtime.rs	Modified conditional compilation attribute to include test feature.
.../wasm-bindings/src/match_pattern.rs	Updated compile function call with an additional boolean argument.

---

Recent Review Details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f1c8bac and 2dbaa94.

Files selected for processing (2)

• crates/core/src/problem.rs (2 hunks)
• crates/wasm-bindings/src/match_pattern.rs (2 hunks)

Files skipped from review as they are similar to previous changes (2)

• crates/core/src/problem.rs
• crates/wasm-bindings/src/match_pattern.rs

Additional Context Used

Learnings (1)

Common

User: morgante
URL: https://github.com/getgrit/gritql/pull/231

Timestamp: 2024-04-15T05:47:47.743Z
Learning: User morgante prefers not to be asked for documentation.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 0

Out of diff range and nitpick comments (2)

crates/wasm-bindings/src/match_pattern.rs (2)

Line range hint 61-61: TODO: Remove temporary initialization line once initialize_tree_sitter function is confirmed to work.

Would you like me to open a GitHub issue to track the removal of this temporary code?

---

Line range hint 183-183: TODO: Improve error handling to capture and report real errors from external function calls.

Would you like me to help improve the error handling mechanism in this function?