fix:port tests from core

[JarbasAl]

Summary by CodeRabbit

• New Features

  • Enhanced intent data retrieval in the adapt service for improved performance.
  • Introduced a comprehensive suite of unit tests to validate intent registration and retrieval.

• Bug Fixes

  • Corrected the method of accessing matched intent data to ensure accuracy.

• Tests

  • Added new test classes and functions to strengthen testing coverage for the adapt service's capabilities.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications to the handle_get_adapt method in the AdaptPipeline class, changing the way intent data is accessed by switching from intent.intent_data to intent.match_data. Additionally, a new test file test/test_intent_service.py has been added, which includes unit tests for the AdaptPipeline and AdaptIntent classes. This test suite utilizes the unittest framework and encompasses various functions and classes aimed at validating intent registration and retrieval processes.

Changes

File Path	Change Summary
ovos_adapt/opm.py	Modified handle_get_adapt method to access intent data using intent.match_data instead of intent.intent_data.
test/test_intent_service.py	Introduced a new test file with unit tests for AdaptPipeline and AdaptIntent, including test classes and utility functions for intent handling.

Possibly related PRs

• fix:standardize_lang #10: The changes in the AdaptPipeline class in ovos_adapt/opm.py are related as both PRs modify the same class, specifically the handle_get_adapt method in the main PR and the match_intent method in the retrieved PR, indicating a focus on intent handling and data retrieval.

Poem

In the burrow where intents play,
A change was made, hip-hip-hooray!
From intent_data to match_data we hop,
With tests to ensure we never stop.
So let’s celebrate this code delight,
With binkies and joy, we’ll code all night! 🐇✨

---

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