Skip to content

Conversation

@MKAbuMattar
Copy link
Collaborator

Pull Request Template for Rawi

Thank you for your contribution to Rawi! Please fill out the following information to help us review your pull request.

Pull Request Checklist

Before submitting your PR, please ensure you have completed the following:

  • I have read the CONTRIBUTING.md guide.
  • I have checked the existing issues and pull requests to ensure this is not a duplicate.
  • My code follows the project's Coding Style.
  • My changes pass all existing tests.
  • I have added new tests for new features or bug fixes (if applicable).
  • I have updated the documentation as needed (if applicable).
  • My commit message follows the Conventional Commits standard.

Type of Change

Please mark the type of change your PR introduces with an x in the brackets (e.g., [x]).

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Chore (e.g., build process, tooling, or CI/CD updates)
  • Refactor (code change that neither fixes a bug nor adds a feature)
  • Other (please describe below)

Description

Please provide a clear and concise description of your changes. What problem does this PR solve? How does it solve it?

Related Issue(s)

If this PR addresses an open issue, please link it here (e.g., Closes #123, Fixes #456).

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Examples:

  • Unit tests: pnpm test
  • Manual testing: Steps followed...
  • End-to-End tests...

Screenshots (if applicable)

If your changes include UI updates or new features that are visually demonstrable, please include screenshots or GIFs here.

Additional Context

Add any other context or information about your pull request here. This could include challenges faced, design decisions, or future considerations.

@MKAbuMattar MKAbuMattar self-assigned this Aug 23, 2025
@MKAbuMattar MKAbuMattar requested a review from a team as a code owner August 23, 2025 19:31
MKAbuMattar and others added 16 commits August 23, 2025 23:06
- Added 'gemini-2.5-flash-image-preview' to Google model IDs.
- Updated Ollama models list with new 'deepseek-v3.1' variants and their respective tags.
- Incremented chat model count from 6592 to 6596 and total model count from 6901 to 6905.
…essors

- Updated `AdvancedSessionOperations`, `SessionSelector`, `SessionManager`, and `ActTemplateManager` classes to use private class fields (e.g., `#sessionManager`, `#profile`) instead of private properties.
- Refactored methods to access these private fields accordingly.
- Improved encapsulation and code readability by utilizing modern JavaScript class field syntax.
…up package resolutions

fix: update generated timestamp in ollama-models-list.ts
- Added 'deepseek-v3.1:latest' to the list of chat models.
- Introduced 'embeddinggemma' and its variants to the embedding models.
- Updated the model counts: chat models increased to 6597, embedding models to 66, and total models to 6912.
- Added new model IDs to the LMStudio provider, including models from Baidu, Bytedance, and Qwen.
- Updated existing model IDs in the LMStudio provider for Google and Mistralai models.
- Introduced a new model ID in the XAI provider.
- Updated the generation timestamp in the Ollama models list.
- Added SearchManager class to manage search providers and handle search requests.
- Integrated DuckDuckGo and Wikipedia as search providers.
- Implemented deduplication of search sources with SourceDeduplicator.
- Created SourceProcessor for processing and analyzing search sources.
- Developed SourceRelevanceFilter to filter sources based on relevance to the query.
- Introduced StyleEngine to apply different report styles to the generated content.
- Defined types for research configuration, search sources, and content analysis.
- Enhanced error handling and logging throughout the search and processing workflow.
@github-actions
Copy link

This pull request is stale because it has been open for 60 days with no activity. Remove the "Stale" label or comment on the pull request, or it will be closed in 7 days.

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